Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 4
- 4 7
- 3 2
- 2 0
- 1 0
Trust in production
- Trust it - 69%
- With caveats - 23%
- Wouldn't - 8%
92% would recommend this server
How reviewers scored it
- Setup & docs 3.8
- Auth experience 4.3
- Reliability 4.2
- Maintainer responsiveness 4.2
Why it got an A
The grade describes Cloudinary's five MCP servers: asset management, environment config, structured metadata, analysis (all with hosted and npm versions) and the hosted MediaFlows server. Hosted ones use OAuth2 by default, with API-key headers as an option, and the local packages take scope filters (admin, builder, librarian) and tool-annotation filters. Source is MIT, with new npm releases daily, about five npm maintainers and no advisories. Biggest caution: the asset server has tools that delete assets, folders and collections (marked destructive in the code), and the docs don't say whether your client asks first, so keep tool approval on and use a narrow scope. The linked repo is README-only (code lives in per-server repos), so this is assessed from the vendor's public docs.
How to connect
Hosted: https://asset-management.mcp.cloudinary.com/mcp (OAuth sign-in). Local: npx -y --package @cloudinary/asset-management-mcp -- mcp startIs Cloudinary MCP Servers safe?
Is Cloudinary MCP Servers safe to use?
Cloudinary MCP Servers grades A: all four checks are at full marks. Strong public trust signals. It is still not a full audit, so give it the narrowest access that works.
Does Cloudinary MCP Servers have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Cloudinary MCP Servers support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Amplitude MCP ServerAmplitude's hosted MCP server for product analytics - search and query events, charts, dashboards, experiments, feature flags, cohorts and session replay, with OAuth sign-in and a separate EU endpoint.
- A Appwrite MCP ServerOfficial Appwrite server that exposes databases, users, functions, teams and storage as tools, hosted with OAuth or run locally with a project API key.
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Better Stack MCP ServerOfficial hosted Better Stack server to read and manage incidents, monitors, status pages and on-call, and run SQL over your logs, spans and metrics, with OAuth or an API token.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
Embed this badge
[](https://trustedmcp.io/servers/cloudinary-mcp)<a href="https://trustedmcp.io/servers/cloudinary-mcp"><img src="https://trustedmcp.io/badge/cloudinary-mcp.svg" alt="TrustedMCP grade A" height="80"></a>Community reviews
Mixed feelings after two weeks
Works well enough for what I need. Scoped the token to just what the agent needs and it respected that.
Used for CI failure investigation
- Setup & docs 2/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
No complaints after a month
Started with it as an experiment, now it is a fixture. Nice to use something maintained by Cloudinary rather than a random fork. Auth is handled properly, and revoking access later was one click. Easy recommendation.
Used for Internal developer assistant
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 3/5
The Cloudinary Servers integration I wanted
Set this up for our team after comparing a few options. You can tell it is actively maintained, the rough edges keep getting fixed. Sign-in flow was painless and I never had to paste a key into a config file. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent.
Used for Generating boilerplate from existing patterns
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Earned a permanent spot in my config
Tried it on a side project first, then rolled it out at work. Sign-in flow was painless and I never had to paste a key into a config file. It is in our production agent and I sleep fine.
Used for Looking up Cloudinary Servers data without leaving the editor
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Better than the DIY script it replaced
Replaced a homegrown script with Cloudinary MCP Servers and have not looked back. Being official from Cloudinary counts for a lot when I pitch it to security. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Worth it, just do not skip the hardening steps.
Used for Code review summaries for pull requests
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
OK for read-only work
Took longer to configure than I expected. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. For anything real I would look elsewhere.
Used for Keeping project tickets in sync with code changes
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Quietly reliable
Of the Cloudinary Servers integrations I tried, this one is the most predictable. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Filed an issue and got a reply within two days. Would recommend without hesitation.
Used for Debugging sessions in Cursor
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Does what it says, no drama
Hooked Cloudinary MCP Servers into Claude Code and it worked on the first try. Narrowing the scopes took ten minutes and made me much happier running it. I like that access goes through a proper sign-in instead of a long-lived secret on disk.
Used for Scripting routine maintenance tasks
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Saves me a context switch every hour
Been running this for about a month now. Narrowing the scopes took ten minutes and made me much happier running it. Sign-in flow was painless and I never had to paste a key into a config file. Good choice if you need Cloudinary Servers in your agent.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Set it up once, forgot about it
Installed it on a Friday, it was part of my workflow by Monday. Sign-in flow was painless and I never had to paste a key into a config file. It is in our production agent and I sleep fine.
Used for Automating release notes
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Good defaults, good docs
Our agents call this dozens of times a day. Scoped the token to just what the agent needs and it respected that. Updates land regularly, and nothing broke when I upgraded. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 3/5
Our team uses it every day
Simple to set up in Cursor, simple to reason about. The OAuth flow worked first time in Claude Code. Scoped the token to just what the agent needs and it respected that. Happy to run it in production.
Used for Looking up Cloudinary Servers data without leaving the editor
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Worth the five minutes to set up
I use this almost daily. Nice to use something maintained by Cloudinary rather than a random fork. Auth is handled properly, and revoking access later was one click. Would recommend without hesitation.
Used for Letting a coding agent open and triage issues
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.