# MongoDB MCP Server

> MongoDB's own MCP server: your agent explores schemas, queries and updates data, suggests indexes and manages Atlas clusters.

The MongoDB MCP Server is MongoDB's official MCP server. It lets your agent work with your MongoDB data and deployments in plain words, on any deployment: MongoDB Atlas, Atlas Local, Community Edition or Enterprise Advanced.

What you can do with it
- List databases and collections, and explain a collection's schema, indexes and storage size
- Run find queries, counts and aggregations, and export the results
- Insert, update and delete documents, and create, rename or drop collections and indexes
- Read explain plans, recent mongod logs and Atlas Performance Advisor suggestions for indexes, schema and slow queries
- Manage Atlas: list and create projects, clusters and database users, set IP access lists, load sample data, read alerts and run Stream Processing
- Create, connect to and delete local Atlas deployments in Docker
- Search MongoDB's documentation and expert guidance through the MongoDB Assistant knowledge base

How it connects
It runs on your machine with npx -y mongodb-mcp-server (Node.js 22.13 or later), or in Docker. Give it a connection string in MDB_MCP_CONNECTION_STRING for the database tools, or Atlas service account credentials in MDB_MCP_API_CLIENT_ID and MDB_MCP_API_CLIENT_SECRET for the Atlas tools. Running npx -y mongodb-mcp-server@latest setup walks you through the configuration. MongoDB recommends passing secrets as environment variables rather than command-line arguments.

Read-only when you want it
Start it with --readOnly (or MDB_MCP_READ_ONLY=true) and only its read, connect and metadata tools are registered; MongoDB's own examples use it by default. You can also switch off tools by name or type with disabledTools, ask for confirmation before tools like drop-database and delete-many, and reject queries that don't use an index with --indexCheck.

Good to know
The Atlas tools only appear when you give it Atlas API credentials, and MongoDB advises granting the service account only the permissions it needs. MongoDB also runs a hosted Atlas Managed MCP Server that you sign in to with OAuth through its mongodb-atlas plugin; this listing is the server you run yourself, which also works with self-managed deployments. It sends usage telemetry to MongoDB unless you set MDB_MCP_TELEMETRY=disabled or DO_NOT_TRACK=1.

- Type: Plugin
- Made by: mongodb
- Category: Databases
- Formats: Local MCP
- Version: 2.1.0
- Website: https://www.mongodb.com/docs/mcp-server/
- Source: https://github.com/mongodb-js/mongodb-mcp-server
- Page: https://pluginboard.ai/plugins/mongodb-mcp

## Works with

- Claude
- GitHub Copilot
- Cursor
- Claude Code
- Codex
- Antigravity
- Gemini CLI
- OpenClaw
- OpenCode
- Hermes Agent

## Install

You'll need:

- `MDB_MCP_ALLOW_REQUEST_OVERRIDES` (optional): When set to true, allows configuration values to be overridden via request headers and query parameters.
- `MDB_MCP_API_CLIENT_ID` (optional): Atlas API client ID for authentication. Required for running Atlas tools.
- `MDB_MCP_API_CLIENT_SECRET` (optional): Atlas API client secret for authentication. Required for running Atlas tools.
- `MDB_MCP_ASSISTANT_BASE_URL` (optional): Base URL for the MongoDB Assistant API.
- `MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS` (optional): Time in milliseconds that temporary database users created when connecting to MongoDB Atlas clusters will remain active before being automatically deleted.
- `MDB_MCP_CONFIRMATION_REQUIRED_TOOLS` (optional): Comma separated values of tool names that require user confirmation before execution. Requires the client to support elicitation.
- `MDB_MCP_CONNECTION_SCOPE` (optional): Visibility scope for MongoDB connections created at runtime. With 'session' (the default), each MCP session only sees the connections it created (plus the shared 'preconfigured' one) and they are closed when the session ends — recommended when the HTTP transport is exposed to multiple clients without authentication. With 'global', connections are shared across all sessions and survive session rotation.
- `MDB_MCP_CONNECTION_STRING` (optional): MongoDB connection string for direct database connections. Optional, if not set, you'll need to call the connect tool before interacting with MongoDB data.
- `MDB_MCP_DISABLE_SERVER_SIDE_JS` (optional): When set to true, disallows the use of server-side JavaScript operators (such as $where, $function, and $accumulator) in query filters and aggregation pipelines.
- `MDB_MCP_DISABLED_TOOLS` (optional): Comma separated values of tool names, operation types, and/or categories of tools that will be disabled.
- `MDB_MCP_DRY_RUN` (optional): When true, runs the server in dry mode: dumps configuration and enabled tools, then exits without starting the server.
- `MDB_MCP_ELICITATION_TIMEOUT_MS` (optional): Time in milliseconds the user has to respond to an elicitation request (such as a tool confirmation prompt) before it fails.
- `MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS` (optional): Time in milliseconds between export cleanup cycles that remove expired export files.
- `MDB_MCP_EXPORT_TIMEOUT_MS` (optional): Time in milliseconds after which an export is considered expired and eligible for cleanup.
- `MDB_MCP_EXPORTS_PATH` (optional): Folder to store exported data files.
- `MDB_MCP_EXTERNALLY_MANAGED_SESSIONS` (optional): When true, the HTTP transport allows requests with a session ID supplied externally through the 'mcp-session-id' header. When an external ID is supplied, the initialization request is optional.
- `MDB_MCP_HEALTH_CHECK_HOST` (optional): Deprecated. Use `monitoringServerHost` instead. Host address to bind the healthCheck HTTP server to (only used when transport is 'http'). If provided, `healthCheckPort` must also be set.
- `MDB_MCP_HEALTH_CHECK_PORT` (optional): Deprecated. Use `monitoringServerPort` instead. Port number for the healthCheck HTTP server (only used when transport is 'http'). If provided, `healthCheckHost` must also be set.
- `MDB_MCP_HTTP_BODY_LIMIT` (optional): Maximum size of the HTTP request body in bytes (only used when transport is 'http'). This value is passed as the optional limit parameter to the Express.js json() middleware.
- `MDB_MCP_HTTP_HEADERS` (optional): Header that the HTTP server will validate when making requests (only used when transport is 'http').
- `MDB_MCP_HTTP_HOST` (optional): Host address to bind the HTTP server to (only used when transport is 'http').
- `MDB_MCP_HTTP_PORT` (optional): Port number for the HTTP server (only used when transport is 'http'). Use 0 for a random port.
- `MDB_MCP_HTTP_RESPONSE_TYPE` (optional): The HTTP response type for tool responses: 'sse' for Server-Sent Events, 'json' for standard JSON responses.
- `MDB_MCP_IDLE_TIMEOUT_MS` (optional): Idle timeout for a client to disconnect (only applies to http transport).
- `MDB_MCP_INDEX_CHECK` (optional): When set to true, enforces that query operations must use an index, rejecting queries that perform a collection scan.
- `MDB_MCP_LOG_PATH` (optional): Folder to store logs.
- `MDB_MCP_LOGGERS` (optional): Comma separated values of logger types.
- `MDB_MCP_MAX_ACTIVE_CONNECTIONS` (optional): Maximum number of MongoDB connections a single scope (an MCP session by default, see connectionScope) can hold open. When exceeded, the scope's least-recently-used connection is closed and its connectionId revoked. The preconfigured connection does not count towards the limit.
- `MDB_MCP_MAX_BYTES_PER_QUERY` (optional): The maximum size in bytes for results from a find or aggregate tool call. This serves as an upper bound for the responseBytesLimit parameter in those tools.
- `MDB_MCP_MAX_DOCUMENTS_PER_QUERY` (optional): The maximum number of documents that can be returned by a find or aggregate tool call. For the find tool, the effective limit will be the smaller of this value and the tool's limit parameter.
- `MDB_MCP_MAX_SESSIONS` (optional): Maximum number of concurrent sessions the HTTP transport will hold in memory (only used when transport is 'http'). Each session holds a full server instance, transport, and timers, so choose a value based on your deployment's available memory; the default is a conservative safety net rather than a recommended production value.
- `MDB_MCP_MAX_TIME_M_S` (optional): The maximum time in milliseconds that operations are allowed to run on the MongoDB server. When set, this value is passed as the maxTimeMS option to read operations such as find, aggregate, and count.
- `MDB_MCP_MCP_CLIENT_LOG_LEVEL` (optional): Minimum severity level for log messages forwarded to the MCP client.
- `MDB_MCP_MONITORING_SERVER_FEATURES` (optional): Features to expose on the monitoring server (only used when transport is 'http' and monitoringServerHost/monitoringServerPort are set).
- `MDB_MCP_MONITORING_SERVER_HOST` (optional): Host address to bind the monitoring HTTP server to (only used when transport is 'http'). If provided, `monitoringServerPort` must also be set.
- `MDB_MCP_MONITORING_SERVER_PORT` (optional): Port number for the monitoring HTTP server (only used when transport is 'http'). If provided, `monitoringServerHost` must also be set.
- `MDB_MCP_NOTIFICATION_TIMEOUT_MS` (optional): Notification timeout for a client to be aware of disconnect (only applies to http transport).
- `MDB_MCP_PREVIEW_FEATURES` (optional): Comma separated values of preview features that are enabled.
- `MDB_MCP_READ_ONLY` (optional): When set to true, only allows read, connect, and metadata operation types, disabling create/update/delete operations.
- `MDB_MCP_TELEMETRY` (optional): When set to disabled, disables telemetry collection.
- `MDB_MCP_TRANSPORT` (optional): Either 'stdio' or 'http'.
- `MDB_MCP_VOYAGE_API_KEY` (optional): API key for Voyage AI embeddings service (required for creating Atlas Local deployments with auto-embed vector search capabilities).

Replace each `<NAME>` placeholder with your own value.

### Claude

Add to claude_desktop_config.json:

```json
{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server@2.1.0"
      ]
    }
  }
}
```

### GitHub Copilot

Add to VS Code: vscode:mcp/install?%7B%22name%22%3A%22mongodb-mcp-server%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22mongodb-mcp-server%402.1.0%22%5D%7D

Run in your terminal:

```shell
code --add-mcp '{"name":"mongodb-mcp-server","command":"npx","args":["-y","mongodb-mcp-server@2.1.0"]}'
```

Copilot CLI:

```shell
copilot mcp add mongodb-mcp-server -- npx -y mongodb-mcp-server@2.1.0
```

### Cursor

Add to Cursor: cursor://anysphere.cursor-deeplink/mcp/install?name=mongodb-mcp-server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIm1vbmdvZGItbWNwLXNlcnZlckAyLjEuMCJdfQ%3D%3D

Add to .cursor/mcp.json:

```json
{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server@2.1.0"
      ]
    }
  }
}
```

### Claude Code

Run in your terminal:

```shell
claude mcp add mongodb-mcp-server -- npx -y mongodb-mcp-server@2.1.0
```

### Codex

Run in your terminal:

```shell
codex mcp add mongodb-mcp-server -- npx -y mongodb-mcp-server@2.1.0
```

### Antigravity

Add to ~/.gemini/config/mcp_config.json:

```json
{
  "mcpServers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server@2.1.0"
      ]
    }
  }
}
```

### Gemini CLI

Run in your terminal:

```shell
gemini mcp add mongodb-mcp-server npx -y mongodb-mcp-server@2.1.0
```

### OpenClaw

In a terminal: Run openclaw mcp add mongodb-mcp-server --command npx, with --arg before each argument (-y mongodb-mcp-server@2.1.0) and --env NAME=value for each variable it needs.

### OpenCode

Run in your terminal:

```shell
opencode mcp add mongodb-mcp-server -- npx -y mongodb-mcp-server@2.1.0
```

### Hermes Agent

Add to ~/.hermes/config.yaml:

```json
{
  "mcp_servers": {
    "mongodb-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mongodb-mcp-server@2.1.0"
      ]
    }
  }
}
```

---
From Pluginboard (https://pluginboard.ai).
