Cloudinary MCP

Live

OAUTH 2.0

MEDIA

Media

Connects AI agents to Cloudinary's asset management platform, enabling upload, search, transformation, and organization of media assets through natural...

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Cloudinary MCP
agent · Acme Q3
Run
Asset Rename in Cloudinary MCP
cloudinarymcp_asset_rename
85ms
Message Claude...

Cloudinary MCP tools for AI agents

CALL ANY TOOL
12 tools covering asset, create.
cloudinarymcp_asset_rename
Updates an existing asset's identifier (public id) and optionally other metadata in your cloudinary account.
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="cloudinarymcp")

mcp = MultiServerMCPClient({
    "cloudinarymcp": {
        "url": "https://mcp.scalekit.com/cloudinarymcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()
import OpenAI from "openai";
const token = await client.agent.getToken({ userId: "user_id", connector: "cloudinarymcp" });
// Connect to MCP at https://mcp.scalekit.com/cloudinarymcp
import Anthropic from "@anthropic-ai/sdk";
const token = await client.agent.getToken({ userId: "user_id", connector: "cloudinarymcp" });
// Connect to MCP at https://mcp.scalekit.com/cloudinarymcp
from google.adk.agents import LlmAgent
token = client.agent.get_token(user_id="user_id", connector="cloudinarymcp")
# Connect to MCP at https://mcp.scalekit.com/cloudinarymcp
Try these prompts
Paste any prompt into your agent to get started.
Finds images in your asset library based on visual similarity or content?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Cloudinary MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Cloudinary MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Cloudinary MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Cloudinary MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
No items found.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Cloudinary as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Cloudinary OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Cloudinary?
Yes. Pass a tool name filter to listScopedTools so the media agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Cloudinary.

What happens when a user revokes Cloudinary access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Which media assets can the agent transform or delete?
Only assets the authorizing user can manage in Cloudinary. Uploads, renames, and deletions follow the user's product environment permissions, and destructive tools can be filtered out entirely.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""cloudinarymcp"": {
""url"": ""https://mcp.scalekit.com/cloudinarymcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.cloudinarymcp]
url = ""https://mcp.scalekit.com/cloudinarymcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""cloudinarymcp"": {
""url"": ""https://mcp.scalekit.com/cloudinarymcp"",
""type"": ""http""
}
}
}