Manage Uploadcare files, groups and webhooks; upload and store files. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Uploadcare connector, then ask in plain words. The AI picks the tools.
For developers and content teams who store images and files in Uploadcare.
The AI lists files in the project, and opens one to read its name, size, type, whether it is an image, tags and metadata.
The AI reads the project name, public key, collaborators and autostore setting, and lists file groups.
The AI uploads a file from a public URL into the project. It can also mark an existing file, by its UUID, as stored so it is kept.
Changes dataThe AI finds a file and deletes it from the project for good. Confirm the file first.
Changes dataThe AI lists the webhook subscriptions of the project and can create a new one that posts to a target URL when an event fires.
Changes dataThe 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.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
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"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+ | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Uploadcare server only. Ask your AI to run uploadcare_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with uploadcare_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with uploadcare_upgrade before then undoes the cancel. Or write to [email protected].
uploadcare_get_projectuploadcare_list_filesuploadcare_get_fileuploadcare_get_file_metadatauploadcare_list_groupsuploadcare_get_groupuploadcare_list_webhooksuploadcare_upload_from_urluploadcare_store_fileuploadcare_delete_fileuploadcare_create_webhookuploadcare_usage_statusuploadcare_request_featureuploadcare_upgradeuploadcare_cancel_subscriptionBrowse your latest uploaded files. Check project details and file groups. Upload a file from a URL, or keep a file stored. Delete files you no longer need. Review and add webhooks. See what you can do for the details.
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.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
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 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Uploadcare server only. Cancel any time: your paid plan then runs to the end of the paid period. Run uploadcare_usage_status to see how many calls you used.
Ask the AI to run uploadcare_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run uploadcare_cancel_subscription. Your paid plan 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, ChatGPT, Codex, 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.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.