Integrations · Content

Connect Cloudinary to Well

Index Cloudinary Cloudinary MCP server so your agents can search across them alongside the rest of your workspace.

What Well pulls from Cloudinary

Cloudinary feeds Cloudinary MCP server into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Cloudinary’s access.

From Cloudinary		In Well	Relation
Cloudinary MCP server		Workspace context	Reachable from

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Cloudinary → Well

What Well does with your Cloudinary connection

Connect

Connect Cloudinary over OAuth (MCP DCR): Well registers a client through Cloudinary's OAuth Dynamic Client Registration and you approve on Cloudinary's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Connecting Cloudinary makes it reachable from your workspace; Cloudinary exposes no structured records for Well to sync into the data model today.

Enrich

With no records to ingest, Cloudinary adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.

Available

Cloudinary is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.

Questions Cloudinary unlocks

Ask in plain language. Well answers from your connected Cloudinary connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Cloudinary connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Cloudinary connection…

Connect Cloudinary in three steps

01
Connect Cloudinary over its MCP server
Choose Cloudinary in Well's Connections panel and authorise it through its MCP server at asset-management.mcp.cloudinary.com over OAuth. Well registers a client via Dynamic Client Registration and walks you through Cloudinary's consent step, with no keys to paste.
- AuthOAuth (MCP DCR)
- MCP serverasset-management.mcp.cloudinary.com/sse
02
Make it reachable
The connection puts Cloudinary within reach of your workspace and its agents. Cloudinary does not expose financial entities for Well to map today, so there is no invoice, transaction, or account sync to configure; Well will not invent one to fill the step.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to reach Cloudinary from the same place your agents reach the rest of your stack. If Cloudinary later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records rather than placeholder claims.
- Availabilityreachable as soon as connect completes

The OAuth handshake completes in about a minute. This is a reach-and-availability connection, not a data feed, so nothing backfills.

How Cloudinary stays secure with Well

Cloudinary connects over its MCP server, with OAuth Dynamic Client Registration handling the credential so Well never holds a Cloudinary secret. Because no structured financial entity is mapped today, the token simply makes Cloudinary reachable from your workspace rather than pulling records. The connection is read-only and grants Well nothing it could change in Cloudinary.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsasset-management.mcp.cloudinary.com/sse

Read Cloudinary records
Resources the Cloudinary MCP server exposes, scoped by your OAuth approval.
granted
Resolve Cloudinary MCP server across your stack
Match identifiers in Cloudinary against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Cloudinary records
Not granted; Cloudinary is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Cloudinary passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Cloudinary’s admin panel.

Frequently asked questions about Cloudinary and Well

Choose Cloudinary in Well's Connections panel and authorise it through its MCP server over OAuth. Well registers a client via Dynamic Client Registration and walks you through Cloudinary's consent step, with no keys to paste. The connection puts Cloudinary within reach of your workspace and agents.

Nothing structured, and Well is candid about that. Cloudinary does not expose financial entities for Well to map, so there is no invoice, transaction, or account sync to set up. The connector exists so Cloudinary can be reached alongside your other tools; richer structured sync would depend on Cloudinary exposing the kind of data Well captures, which it does not today.

The connection lets agents in your workspace reach Cloudinary in the same place they reach the rest of your stack, rather than treating it as a separate silo. It is a reach-and-availability connector, not a data feed: useful for keeping one connected surface, honest about not pulling structured records that are not there.

Only if and when Cloudinary exposes structured entities through its MCP server that map onto what Well captures. Until then, Well will not invent a synced record to make the page look fuller; the connection stays an availability link. If that changes, the data-flow section would reflect the real entities rather than placeholder claims.

Disconnect Cloudinary in Well and the OAuth token is revoked and the MCP reach ends immediately. Because nothing structured was being synced, there are no workspace records to retain or purge from the connection. It simply removes Cloudinary from the set of tools your agents can reach through Well.