uploadcare
Server Details
Manage Uploadcare files, groups and webhooks; upload and store files.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
11 toolsuploadcare_create_webhookCreate webhookDestructiveInspect
Creates a webhook subscription (additive). The project will POST to target_url when the chosen event fires. REST API: POST /webhooks/.
| Name | Required | Description | Default |
|---|---|---|---|
| event | No | Event to subscribe to. Default "file.uploaded". | |
| is_active | No | Whether the webhook is active. Default true. | |
| target_url | Yes | URL the webhook will POST to. |
uploadcare_delete_fileDelete fileDestructiveInspect
Permanently deletes a file from the project. Destructive. REST API: DELETE /files/{uuid}/.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | File UUID to delete. |
uploadcare_get_fileGet fileRead-onlyInspect
Get full info for a single file: uuid, url, original_filename, size, mime_type, is_image, is_ready, timestamps, variations, content_info, metadata, tags. REST API: GET /files/{uuid}/.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | File UUID. |
uploadcare_get_file_metadataGet file metadataRead-onlyInspect
Get all custom metadata key/value pairs for a file. REST API: GET /files/{uuid}/metadata/.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | File UUID. |
uploadcare_get_groupGet groupRead-onlyInspect
Get info for a single file group by its id. REST API: GET /groups/{uuid}/.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | Group id in the form "<uuid>~<count>", e.g. "badfc9f7-...~2". |
uploadcare_get_projectGet projectRead-onlyInspect
Get project details: name, public key, collaborators, and whether autostore is enabled. REST API: GET /project/.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
uploadcare_list_filesList filesRead-onlyInspect
List files in the project (paginated envelope: next, previous, total, per_page, results). REST API: GET /files/.
| Name | Required | Description | Default |
|---|---|---|---|
| from | No | Pagination cursor taken from a previous response's `next` URL. | |
| limit | No | Files per page (max 1000). Default 100. | |
| stored | No | Filter by stored status (true = stored, false = not stored). | |
| removed | No | Filter by removed status (true = removed, false = present). | |
| ordering | No | Sort order, e.g. datetime_uploaded or -datetime_uploaded (descending). |
uploadcare_list_groupsList groupsRead-onlyInspect
List file groups in the project (paginated envelope: next, previous, total, per_page, results). REST API: GET /groups/.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Groups per page (max 1000). Default 100. | |
| ordering | No | Sort order, e.g. datetime_created or -datetime_created (descending). |
uploadcare_list_webhooksList webhooksRead-onlyInspect
List all webhook subscriptions configured for the project. REST API: GET /webhooks/.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
uploadcare_store_fileStore fileDestructiveInspect
Marks a file as permanently stored (otherwise unstored files are deleted after 24h). Additive. REST API: PUT /files/{uuid}/storage/.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | File UUID to store. |
uploadcare_upload_from_urlUpload file from URLDestructiveInspect
Uploads a file into the project from a public URL (additive). Uses the Upload API host with the public key. Returns { type: "token", token } for async ingestion (poll separately) or the file info. Upload API: POST /from_url/.
| Name | Required | Description | Default |
|---|---|---|---|
| store | No | Store the file: "1" = store, "0" = don't store, "auto" = project default. Default "auto". | |
| filename | No | Override the stored filename. | |
| source_url | Yes | Public URL of the file to ingest. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!