Connect Cloudinary to Claude Code

Search, upload, tag, organize and delete images and videos in a Cloudinary product environment, and read its usage. Add Toolspoke to Claude Code once and it can use 15 Cloudinary actions. Your Cloudinary credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Cloudinary and connect it

    Add Cloudinary to a project in your Toolspoke workspace.

    API key and secret. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Cloud name
    Cloudinary Console → Settings → API Keys. The cloud name is shown at the top of that page.
    API key and API secret
    Cloudinary Console → Settings → API Keys → Generate New API Key. Paste the API key, a colon, then the API secret. It is sent as HTTP Basic. A key created with a restricted role is limited to that role's permissions.
  3. Choose what Claude Code may do

    All 15 actions start on. Switch off any of the 6 actions that change something in Cloudinary, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Cloudinary actions that only read, so they are safe to try first.

  • List the assets of one resource type that carry a given tag
  • List the assets placed in one asset folder (dynamic folder mode), of every resource type
  • List the top-level folders of the product environment
  • List the folders directly inside a folder

What Claude Code can do in Cloudinary

9 actions read, 4 write and 2 delete or permanently change something.

Reads

  • Get usage

    Report the product environment's plan, credits, storage, bandwidth, transformations, request counts and asset counts. It takes no arguments and needs a working key and the right cloud name, which is why an install tests itself with it.

  • List resources

    List assets of one resource type and delivery type, newest first, optionally only those whose public ID starts with a prefix or that were created after a date. Paged by next_cursor.

  • Get resource

    Read one asset by public ID, format, size, dimensions, URLs, tags, context, structured metadata and derived versions.

  • Search assets

    Search every asset with a Lucene-like expression over public_id, folder, asset_folder, tags, context, format, bytes, width, created_at and more, e.g. 'tags:shoe AND format:png', 'uploaded_at>1w', 'asset_folder="Marketing"'. Paged by next_cursor.

  • List resources by tag

    List the assets of one resource type that carry a given tag.

  • List resources in folder

    List the assets placed in one asset folder (dynamic folder mode), of every resource type.

  • List root folders

    List the top-level folders of the product environment.

  • List subfolders

    List the folders directly inside a folder.

  • List tags

    List the tags in use on assets of one resource type, optionally only those starting with a prefix.

Writes

  • Upload from url

    Upload an asset from a public HTTPS URL (or a data URI). It never overwrites an existing asset with the same public ID, that is fixed to false here, so an upload cannot replace something already in use.

  • Update resource

    Update one asset's tags, contextual metadata, structured metadata, display name or folder. tags replaces the asset's whole tag list. context and metadata are pipe-separated key=value pairs, e.g. alt=Red shoe|caption=Sale.

  • Rename resource

    Change an asset's public ID, which changes its delivery URL, anything linking to the old URL breaks. It never overwrites an asset already at the new ID; that is fixed to false here.

  • Create folder

    Create an empty folder, including any missing parents in the path.

Deletes or permanently changes

  • Delete resources

    Delete up to 100 assets by public ID, with their derived versions. Any page still using their URLs breaks; recovery is only possible if backups are enabled on the account.

  • Delete folder

    Delete an empty folder. Cloudinary refuses a folder that still holds assets, so delete or move them first.

Cloudinary in Claude Code: questions

Does Claude Code see my Cloudinary credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Cloudinary?

Yes. Each of the 15 actions can be switched off for a project. Turn off the 6 that change something and Claude Code can only read.

Will 15 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Cloudinary action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Cloudinary call does not run in a sandbox, so it bills nothing.

Try Cloudinary in Claude Code

Free to start, and tool calls cost nothing on any plan.