Uploadcare MCP server

What the model can do

Uploadcare file uploads and storage: the project, files by upload date, stored or removed state, file details (type, size, dimensions, tags, metadata key names), search by name, metadata, type, tags, size or date, and file groups; when you ask, can store or permanently delete files, copy a file, set or delete a metadata key, add, remove or replace tags, and delete a group.

Reads

• uploadcare_projectThe Uploadcare project: its name, public key, whether uploads are stored automatically, how many collaborators it has, and file totals (stored…
• uploadcare_filesFiles in the project by upload date, oldest first from a date or newest first, with name, type, size, dimensions, state (stored, temporary, removed)…
• uploadcare_fileOne file by uuid: name, type, size, dimensions or duration, upload, store and removal dates, tags and metadata key names, and how many variations…
• uploadcare_search_filesSearch files by words (in names, metadata and type, at least 4 characters), exact metadata values, tags, images only, size or upload date.
• uploadcare_groupsFile groups (sets of files uploaded together), newest first or oldest first from a date, with id, creation date and file count.
• uploadcare_groupOne file group by id (<uuid>~<count>) with its files (removed files show as removed).

Acts, when you ask

These change something in Uploadcare. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• uploadcare_store_filesStores files in Uploadcare so they are kept permanently (a file that is not stored is removed 24 hours after upload)…
• uploadcare_delete_filesPermanently deletes files from Uploadcare storage; their CDN copies stop serving everywhere at once, so any page or app using them breaks.
• uploadcare_copy_fileCopies a file (by uuid) into the project's own storage as a new file with a new uuid; stored if store is true, else temporary for 24 hours.
• uploadcare_set_metadataSets one metadata key on an Uploadcare file, creating it or overwriting its value (the old value is lost).
• uploadcare_delete_metadataDeletes one metadata key from an Uploadcare file; its value is gone.
• uploadcare_update_tagsAdds and/or removes tags on an Uploadcare file (removals first, then additions; tags are lowercased; at most 50 per file).
• uploadcare_replace_tagsReplaces all of an Uploadcare file's tags with exactly the list given (an empty list clears them).
• uploadcare_delete_groupPermanently deletes an Uploadcare file group; the files that were in it are kept as they are, but the group's own CDN link stops working.

Connect it

First connect Uploadcare on Dashboard → Connections, then add Memtro to your client once. The Uploadcare tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Uploadcare connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which files uploaded this week are still temporary?
• › How many files are stored in the project?
• › Find the images tagged hero.
• › Which files were removed last month?
• › Store the files uploaded this morning.

Questions

Is this an official Uploadcare MCP server?

No. It is Memtro's MCP server with Memtro's Uploadcare connector behind it: the connector reads Uploadcare through its API with the credentials you connect on Dashboard → Connections, and Uploadcare publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Uploadcare?

Only when you ask, and only what it has been granted: store files so they are kept permanently; permanently delete files; copy a file within the project; set a file's metadata key; delete a file's metadata key; add or remove a file's tags; replace a file's tags; delete a file group (its files are kept). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Content and web

• Ahrefs MCP server
• WordPress MCP server
• Webflow MCP server
• Typeform MCP server
• Eventbrite MCP server
• Contentful MCP server