Manage Uploadcare files, groups and webhooks; upload and store files. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"uploadcare": {
"url": "https://uploadcare.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"uploadcare": {
"type": "http",
"url": "https://uploadcare.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Uploadcare Public key and Uploadcare Secret key.
Find both in the Uploadcare dashboard → API keys (per project). Your keys are used only to call the API on your behalf and to derive a private account id; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Uploadcare Public key and Uploadcare Secret key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Uploadcare connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
uploadcare_get_project | read | Get project Get project details: name, public key, collaborators, and whether autostore is enabled. REST API: GET /project/. |
uploadcare_list_files | read | List files List files in the project (paginated envelope: next, previous, total, per_page, results). REST API: GET /files/. |
uploadcare_get_file | read | Get file 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}/. |
uploadcare_get_file_metadata | read | Get file metadata Get all custom metadata key/value pairs for a file. REST API: GET /files/{uuid}/metadata/. |
uploadcare_list_groups | read | List groups List file groups in the project (paginated envelope: next, previous, total, per_page, results). REST API: GET /groups/. |
uploadcare_get_group | read | Get group Get info for a single file group by its id. REST API: GET /groups/{uuid}/. |
uploadcare_list_webhooks | read | List webhooks List all webhook subscriptions configured for the project. REST API: GET /webhooks/. |
uploadcare_upload_from_url | write | Upload file from URL 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/. |
uploadcare_store_file | write | Store file Marks a file as permanently stored (otherwise unstored files are deleted after 24h). Additive. REST API: PUT /files/{uuid}/storage/. |
uploadcare_delete_file | write | Delete file Permanently deletes a file from the project. Destructive. REST API: DELETE /files/{uuid}/. |
uploadcare_create_webhook | write | Create webhook Creates a webhook subscription (additive). The project will POST to target_url when the chosen event fires. REST API: POST /webhooks/. |
uploadcare_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
uploadcare_request_feature | Request a missing feature Tell usefulapi that the user needs something the Uploadcare tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
uploadcare_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Uploadcare tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
uploadcare_cancel_subscription | Cancel the Pro subscription Cancel the caller's Uploadcare Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run uploadcare_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Uploadcare server only. Subscribe with uploadcare_upgrade (it returns a Stripe Checkout link). Cancel any time with uploadcare_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running uploadcare_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Uploadcare. The server calls the Uploadcare API with your own Uploadcare access, so it sees only the data that your account can see.
The login page asks for your Uploadcare Public key and Uploadcare Secret key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Uploadcare Public key and Uploadcare Secret key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Uploadcare API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Uploadcare.
Yes, if you approve it. 4 of the 11 Uploadcare tools can create or change data. The other 7 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Uploadcare server only. Run uploadcare_usage_status to see how many calls you used.
Ask the AI to run uploadcare_upgrade: it returns a Stripe Checkout link. To cancel, run uploadcare_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with uploadcare_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.