MongoDB Atlas (Managed MCP)

MongoDB’s own Atlas Managed MCP Server (https://mcp.mongodb.com), passed through by Cendriix. MongoDB owns the tool surface — the Atlas control plane plus the database tools — so a tool MongoDB ships arrives here without a Cendriix release. There is no connection string and no IP allowlist.

Overview

Which MongoDB integration do I want?

Cendriix has three, and their credentials are not interchangeable.

Pick this page’s integration for Atlas. Use the connection-string MCP for self-managed clusters, or for Atlas clusters you do not want to expose to Atlas’s own delegated-access platform.

Prerequisite: enable AI client access in Atlas

Atlas disables AI client access by default for existing organizations, and for new organizations created by an existing Atlas user. Until an Organization Owner enables it, Atlas rejects the consent request with “This authorization request is invalid” — before it ever looks at Cendriix.

An Organization Owner must:

1. Open Organization Settings → App Connections in the Atlas UI.
2. Set the access mode: Read (recommended) or Read and write.
3. Save.

Notes worth knowing before you enable it:

• The mode applies to the whole organization; Atlas has no per-user, per-cluster, or per-client setting. Enabling it enables every current and future AI client that supports delegated access.
• Effective access is the more restrictive of the org mode and the authorizing user’s own Atlas permissions. The mode can only reduce access, never widen it.
• In Read mode, write tools are not registered at all — the agent cannot see them.
• The authorizing user needs one of ORG_OWNER, GROUP_OWNER, GROUP_DATA_ACCESS_ADMIN, GROUP_DATA_ACCESS_READ_WRITE, GROUP_DATA_ACCESS_READ_ONLY, or GROUP_STREAM_PROCESSING_OWNER.
• Atlas ends delegated access after 7 days of inactivity or 30 days from consent, whichever comes first; Cendriix then asks you to reconnect. An Organization Owner can shorten that maximum lifetime.
• An Organization Owner cannot revoke one user’s connection — only disable AI client access for the whole organization. Individual users revoke their own from Atlas, or from Cendriix.

Setup — browser consent (recommended)

1. Go to Settings → Integrations → MCPs → MongoDB Atlas (Managed MCP).
2. Choose who the connection is for:
   • Just me — every call is attributed to you in the Atlas audit log, bounded by your own Atlas permissions.
   • Everyone in this workspace — what schedules, triggers, and unattended agents use, since they cannot open a browser.
3. Click Connect with MongoDB. Atlas signs you in and shows a consent screen.
4. Authorize. You land back in Cendriix with the connection shown as Connected, including who connected it, when, and when it expires.

Tokens are envelope-encrypted with your tenant key, refreshed automatically five minutes before expiry, and never returned by any API. See Connect an MCP with OAuth for the mechanics, per-user vs workspace precedence, and error reasons.

Setup — Atlas remote-MCP client credentials

Use this when you want a non-interactive service identity, or your organization has not enabled App Connections. Requires Atlas CLI 1.58.0 or later.

atlas auth login
 
# One organization (or use createGroupMcpConfig for a single project).
# Scope roles read-only — that Atlas grant, not Cendriix, is the real ceiling.
atlas api remoteMcpConfigurations createOrgMcpConfig
 
# Atlas returns the secret ONCE. Lose it and you generate a new one.
atlas api remoteMcpConfigurations createOrgMcpSecret \
  --secretExpiresAfterHours 8760

Paste the pair into the install panel as MDB_MCP_API_CLIENT_ID and MDB_MCP_API_CLIENT_SECRET. Cendriix exchanges them for a short-lived Atlas access token per call and never stores a token.

Precedence: when both exist, a grant wins — your own first, then the workspace-wide one, then the pasted client credentials. This is deliberate: user-delegated calls are attributed to a human in Atlas’s audit log, which a shared service account cannot do.

Tools

MongoDB owns this list; Cendriix passes it through. Run a connect tool first — the database tools operate on a connectionId, not a pasted URI.

Tool names are MongoDB’s hyphenated names, so anything written for the official server works here unchanged.

Read-only enforcement

Two independent layers, plus Atlas’s own:

• Cendriix refuses any tool outside the read set with 403 write_disabled and makes zero outbound requests, unless writes are enabled for the environment.
• Atlas registers only read tools when the organization’s access mode is Read.
• Your Atlas roles bound everything above — scope the remote-MCP configuration, or the authorizing user, to read-only roles.

MongoDB labels aggregate, aggregate-db, and export as read tools even though a $out or $merge stage in a pipeline writes. Read-only Atlas roles are the only hard guarantee.

Rotation and revocation

Every tool invocation is recorded in the Cendriix Audit Log, and Atlas records its own audit events attributed to the authorizing user.

Troubleshooting

Further reading

• Connect an MCP with OAuth — the shared consent capability
• MongoDB MCP — the connection-string integration
• MongoDB Remote MCP Server  — MongoDB’s docs
• Atlas App Connections  — MongoDB’s delegated-access platform