mongodb-atlas-mcp-remote lets your MCP client connect to the MongoDB Atlas Remote MCP server using credentials from your Atlas MCP configuration.
Use this for MCP clients that don't yet natively support service-account (OAuth client-credentials) authentication.
-
Node.js 20.19+, 22.13+, or 24+.
-
A Client ID and Client Secret from a MongoDB Atlas MCP configuration. Creating an MCP configuration in Atlas provisions a dedicated Client ID and Client Secret that is used to authenticate to the Remote MCP server. Creating one requires the Organization Owner or Project Owner role.
Note: These credentials are generated specifically for the Remote MCP server and are different from the standard Atlas API service-account credentials used by the local
mongodb-mcp-serverpackage.
The wrapper is configured with two environment variables:
| Variable | Description |
|---|---|
MDB_MCP_API_CLIENT_ID |
The Client ID from your Atlas MCP configuration. |
MDB_MCP_API_CLIENT_SECRET |
The Client Secret from your Atlas MCP configuration. |
Add the server to your MCP client's configuration. The file location and format vary by client — examples for common clients are below. In each case, replace the placeholder credentials with your own.
Add to .mcp.json:
{
"mcpServers": {
"MongoDB": {
"command": "npx",
"args": ["-y", "mongodb-atlas-mcp-remote@latest"],
"env": {
"MDB_MCP_API_CLIENT_ID": "your-client-id",
"MDB_MCP_API_CLIENT_SECRET": "your-client-secret"
}
}
}
}Add to .cursor/mcp.json:
{
"mcpServers": {
"MongoDB": {
"command": "npx",
"args": ["-y", "mongodb-atlas-mcp-remote@latest"],
"env": {
"MDB_MCP_API_CLIENT_ID": "your-client-id",
"MDB_MCP_API_CLIENT_SECRET": "your-client-secret"
}
}
}
}Add to ~/.codex/config.toml:
[mcp_servers.MongoDB]
command = "npx"
args = ["-y", "mongodb-atlas-mcp-remote@latest"]
[mcp_servers.MongoDB.env]
MDB_MCP_API_CLIENT_ID = "your-client-id"
MDB_MCP_API_CLIENT_SECRET = "your-client-secret"This package is part of the mongodb-mcp-server monorepo. See the Contributing Guide for development setup.