Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Uploadcare (BYOK) — connector documentation

  • MCP endpoint: https://byok-uploadcare.connectorbay.com/mcp
  • REST API: POST https://byok-uploadcare.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-uploadcare.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Uploadcare public and secret key joined as PUBLIC_KEY:SECRET_KEY (paste them as one value with a colon), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-uploadcare.connectorbay.com/health · Tool schemas: https://byok-uploadcare.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-uploadcare · agent@connectorbay.com

What Uploadcare (BYOK) is for

Uploadcare (BYOK) lets an AI assistant read your own Uploadcare data through the Uploadcare API with a key you supply (public and secret key joined as PUBLIC_KEY:SECRET_KEY (paste them as one value with a colon)). Read-only: 7 tools (get_project, list_files, get_file, get_file_metadata, get_file_tags, list_groups, get_group). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.uploadcare.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Uploadcare. Uploadcare and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Uploadcare project is my key connected to?"
  • "What files were uploaded to my Uploadcare project recently?"
  • "Show details of Uploadcare file 2d33999d-c74a-4ff9-99ea-abc23496b052"
  • "What metadata is attached to this Uploadcare file?"
  • "Which tags does this Uploadcare file have?"
  • "What file groups exist in my Uploadcare project?"

What it does

  • get_project: Show the Uploadcare project the keys belong to: name, public key and whether files are stored automatically.
  • list_files: List files uploaded to the Uploadcare project with name, type, size, upload and store dates and image size. Up to 1000 per call; the answer has next and total.
  • get_file: Get one Uploadcare file by UUID: name, MIME type, size, dates, tags, image dimensions or video duration and public CDN URL.
  • get_file_metadata: Get the custom key-value metadata attached to an Uploadcare file.
  • get_file_tags: Get the tags of an Uploadcare file.
  • list_groups: List Uploadcare file groups with id, creation date, file count and CDN URL. Up to 1000 per call.
  • get_group: Get one Uploadcare file group by id: creation date, number of files and CDN URL.

BYOK key

You bring your own Uploadcare public and secret key joined as PUBLIC_KEY:SECRET_KEY (paste them as one value with a colon) (https://app.uploadcare.com/projects/-/api-keys/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.uploadcare.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Uploadcare API (api.uploadcare.com) with a BYOK key; documentation: https://uploadcare.com/docs/api/rest. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Uploadcare. Uploadcare and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Uploadcare account.

Built for: Worldwide. Languages: English.