Skip to content

Cloudinary MCP connector

The Cloudinary connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent upload, search, organize and transform the images, videos and files in your Cloudinary product environment, with each person signed in as themselves.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Find every product image tagged spring campaign in the marketing folder

Working in Cloudinary with Elaichi

  • Looked in Cloudinary
Ask anything…
Governance / Audit log Last 24 hours
Cloudinary Looked in Cloudinary Emily Carter · ChatGPT · 9:41 AM Done
Cloudinary Looked in Cloudinary Megan Brooks · Claude · 9:38 AM Done
Cloudinary Looked in Cloudinary Ryan Hayes · Cursor · 9:35 AM Done

How to connect Cloudinary to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Cloudinary MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Cloudinary MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Cloudinary MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Cloudinary MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Cloudinary MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Cloudinary to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Cloudinary through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Cloudinary is logged.

  • Marketing

    Pull campaign images together in one ask

    Ask for every image tagged with a campaign name and get the list back with folders and formats, ready to hand to the agency or drop into a brief.

  • Design

    Upload and tag new assets from a chat

    Send the latest hero images into the right Cloudinary folder, tag them for the launch, and have the agent confirm what landed where.

  • E-commerce

    Resize product photos for every storefront

    Ask for the square, banner and thumbnail versions of a product image and get the transformed URLs without opening Cloudinary.

  • Content

    Find the video you half remember

    Describe a video by subject, length or when it was uploaded and let the agent search Cloudinary and bring back the matches.

  • Web

    Tidy folders before a site refresh

    Move stale images into an archive folder, rename files to match the new page structure, and keep the live folders clean.

  • Brand

    Check that assets carry the right tags

    Ask which images in the brand folder are missing a usage tag or a region tag, then fix them in the same conversation.

Try asking

  • “Find every product image tagged spring campaign in the marketing folder”
  • “Upload these hero images to the homepage folder and tag them launch”
  • “Which videos in the brand folder were added this week?”

What connecting Cloudinary gets you

5 screens from Elaichi, each doing one job for your Cloudinary account.

Elaichi Agent

Ask Elaichi to work across your apps.

Find every product image tagged spring campaign in the marketing folder

Upload these hero images to the homepage folder and tag them launch

Which videos in the brand folder were added this week?

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about your Cloudinary assets in plain language.

Find images, videos and folders by asking, with answers drawn from live Cloudinary records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Cloudinary works in every client through one endpoint.

Claude, ChatGPT, Cursor and Microsoft Copilot reach Cloudinary through one governed endpoint, no SDK, no shared API key.

ElaichiToolboxes
Name Source template Tools Created

Marketing toolbox

Cloudinary · campaign images and tags

Cloudinary starter 18 Mar 4, 2026

Design toolbox

Cloudinary · uploads and folders

— 9 Mar 2, 2026

E-commerce toolbox

Cloudinary · product photos and transformations

— 24 Feb 27, 2026

Content toolbox

Cloudinary · videos and search

Cloudinary starter 6 Feb 19, 2026

Web toolbox

Cloudinary · site assets and renames

— 31 Jan 30, 2026

Brand toolbox

Cloudinary · logos and usage tags

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Cloudinary toolbox.

Marketing, Design and E-commerce each work from a toolbox scoped to their Cloudinary tasks.

ElaichiConnections
Connection Scope Status Access
CL

Cloudinary (Marketing)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CL

Cloudinary (Design)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CL

Cloudinary (E-commerce)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CL

Cloudinary (Content)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
CL

Cloudinary (Web)

Connected by Ryan Hayes

Personal • Active Not shared
CL

Cloudinary (Brand)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

One Cloudinary connection, shared without sharing a credential.

See who connected each Cloudinary account and which teams and members work through it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Cloudinary Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Cloudinary Images Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Cloudinary Images List Toolbox

Audit log

Every Cloudinary change is logged with a name.

When, who, what happened and which asset, in an append-only log you can search.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Cloudinary digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch images

    Cloudinary

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Cloudinary

    Queued

Workflows

A schedule runs the work, you approve it.

New Cloudinary uploads are fetched, grouped and drafted into a digest, approved, then posted back.

Cloudinary health

Refreshed 4 minutes ago · every 15 minutes · from the images collection

Live

Images

1,284 ↓ 12%

Videos

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Images created

Last 14 days

By team

Share of activity

Marketing 34%

Design 27%

E-commerce 21%

Content 18%

Collections and dashboards

Cloudinary health numbers arrive before anyone asks.

Four metrics, 14 days of uploads and a team breakdown, computed with no model involved.

Why connect Cloudinary's MCP server through Elaichi

Cloudinary builds and runs this MCP server. Elaichi sits in front of it, so Cloudinary's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Cloudinary's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Cloudinary's tools at the same Elaichi address as every other connected app. Nobody adds Cloudinary's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Cloudinary sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Cloudinary's server. By default, a tool Cloudinary does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Cloudinary

    Cloudinary builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Cloudinary team.

    support.cloudinary.com/hc/en-us/requests/new

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Cloudinary

All three can connect Cloudinary to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Cloudinary, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Cloudinary tools Allow or restrict single Cloudinary tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Cloudinary call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Questions, answered

How do I connect Cloudinary to Claude?

Connect Cloudinary in Elaichi first: you sign in to your Cloudinary account over OAuth, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the Elaichi endpoint, https://api.elaichi.ai/mcp. From there Claude can work with the images, videos and folders your Cloudinary login already allows.

Does Cloudinary work with ChatGPT and Cursor as well as Claude?

Yes. Once Cloudinary is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, the Elaichi Agent and any other MCP client. You connect Cloudinary once and every client sees it.

What can an AI agent actually do with my Cloudinary assets?

An agent can upload images, videos and files into your Cloudinary folders, search for assets by tag, folder or name, move and rename them, and produce transformed versions such as a resized or cropped image. Short, concrete asks work best, such as asking for every image tagged with a campaign rather than describing the whole project. What is available depends on what your Cloudinary account has set up.

Does connecting Cloudinary give the AI access to my whole product environment?

No. Every call into Cloudinary runs as the person who signed in, so the agent sees only the folders and assets that person can already reach in Cloudinary. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Cloudinary itself grants.

Can my team share one Cloudinary connection?

Yes. One person connects Cloudinary in Elaichi and shares it with a team, and nobody else ever handles a Cloudinary credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every upload or change.

Can I stop an agent from deleting or changing things in Cloudinary?

Yes. Restrictions in Elaichi apply per action, so you can allow searching and uploading in Cloudinary while restricting deletes or renames. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

What happens to a Cloudinary connection when someone leaves?

Offboarding that person in Elaichi ends their access to Cloudinary through every client at once. A shared Cloudinary connection keeps working for everyone else on the team. If you later disconnect Cloudinary in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

Does the Cloudinary MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Cloudinary is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Cloudinary?

Yes. Both let Claude, ChatGPT or Cursor use Cloudinary. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Cloudinary call.

How is Elaichi different from Composio for Cloudinary?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Cloudinary: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Cloudinary in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot