Skip to main content
Glama
ameksike

MongoDB MCP Server

by ameksike

πŸƒ MongoDB MCP Server

A ready-to-use integration of the MongoDB MCP Server with multiple deployment modes β€” from a simple local launcher to a fully secured RBAC gateway with Keycloak authentication.

Explore how to connect AI agents and LLM clients (Claude, VS Code Copilot, Cursor, etc.) to your MongoDB databases through the Model Context Protocol.


πŸ“‹ Table of Contents

#

Section

Description

1

Deployment Modes

Compare the three available modes

2

Quick Start

Get running in 2 minutes (basic mode)

3

Project Structure

Directory layout overview

4

Test Client

Built-in MCP diagnostic client

5

VS Code Copilot

Connect VS Code to the MCP Server

6

Docker Compose

Run the full stack with containers

7

Documentation

Links to detailed guides

8

npm Scripts

All available commands at a glance

9

References

Official docs and specifications


Related MCP server: mcp-mongo

πŸ”€ Deployment Modes

This project supports three deployment modes, each adding a layer of security on top of the previous one:

🟒 Basic Mode β€” Direct Connection

The simplest setup. The MCP Server runs locally and accepts connections without authentication. Best for local development and quick testing.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”           β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚   Client   │──────────>β”‚  MCP Server  β”‚
β”‚   (Agent)  β”‚   :8008   β”‚  (MongoDB)   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜           β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

When to use: Solo development, local experiments, testing tools.

πŸ“– See Quick Start below.


🟑 Proxy Mode β€” OAuth 2.1 Authentication

Adds Keycloak as an OAuth 2.1 Authorization Server and a reverse proxy that validates Bearer tokens before forwarding to the MCP Server. Implements the Delegated Authorization pattern.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  Bearer  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”           β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚   Client   │──token──>β”‚  Proxy   │──────────>β”‚  MCP Server  β”‚
β”‚   (Agent)  β”‚          β”‚  (RS)    β”‚ (no auth) β”‚  (MongoDB)   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜          β””β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”˜           β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                             β”‚ JWKS
                        β”Œβ”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”
                        β”‚ Keycloak β”‚
                        β”‚  (AS)    β”‚
                        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

When to use: Shared environments, multiple users, audit requirements.

πŸ“– See iac/auth-proxy/ for the proxy implementation.


πŸ”΄ Gateway Mode β€” RBAC (Role-Based Tool Filtering)

The most secure mode. Extends Proxy Mode by inspecting MCP messages and filtering tools based on the user's Keycloak realm role. Different users see and can execute different sets of tools.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  Bearer  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”           β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚   Client   │──token──>β”‚ RBAC Gateway │──────────>β”‚  MCP Server  β”‚
β”‚   (Agent)  β”‚          β”‚ :4040        β”‚ (no auth) β”‚  (MongoDB)   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜          β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜           β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β”‚ JWKS + roles
                          β”Œβ”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”
                          β”‚ Keycloak β”‚
                          β”‚  (AS)    β”‚
                          β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Role

Mode

Access Level

πŸ”‘ mcp-admin

allow

Full access β€” all tools (RW)

πŸ“Š mcp-analyst

allow

14 specific tools (RO)

πŸ‘οΈ mcp-viewer

allow

5 specific tools (RW)

πŸ‘€ mcp-guest

deny

All except atlas category (RO)

When to use: Production, teams with different access levels, compliance.

πŸ“– See doc/gateway.md for the full guide: architecture, step-by-step setup, Keycloak curl examples, token inspection, and RBAC configuration.


πŸš€ Quick Start

Prerequisites

  • Node.js v18+

  • A MongoDB connection string (Atlas or local)

1. Install dependencies

npm install

2. Configure environment

cp .env.example .env

Edit .env and set your MongoDB connection string:

MDB_MCP_CONNECTION_STRING=mongodb+srv://user:password@cluster.mongodb.net

3. Start the MCP Server

npm run mcp:wrapper:start
========================================
  MongoDB MCP Server
========================================
  Status   : running
  URL      : http://127.0.0.1:8008
  Endpoint : http://127.0.0.1:8008/mcp
========================================

4. Verify with the test client

npm run mcp:client:start

All 7 diagnostic checks should pass (connect, ping, list tools, call tool, list resources, read resource, shutdown).


πŸ“ Project Structure

mongodb-mcp/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ wrapper/                 # 🟒 MCP Server launcher
β”‚   β”‚   β”œβ”€β”€ index.js             #    Entry point
β”‚   β”‚   └── McpServerLauncher.js #    Process manager (env, spawn, shutdown)
β”‚   β”œβ”€β”€ gateway/                 # πŸ”΄ RBAC Gateway (OOP, SOLID/GRASP)
β”‚   β”‚   β”œβ”€β”€ index.js             #    Entry point β€” config + startup
β”‚   β”‚   β”œβ”€β”€ GatewayServer.js     #    Controller β€” HTTP server orchestration
β”‚   β”‚   β”œβ”€β”€ TokenVerifier.js     #    JWT/JWKS token verification
β”‚   β”‚   β”œβ”€β”€ RoleResolver.js      #    Role resolution + tool permissions
β”‚   β”‚   β”œβ”€β”€ McpInterceptor.js    #    MCP message filtering/blocking
β”‚   β”‚   └── ProxyHandler.js      #    HTTP reverse proxy to upstream
β”‚   └── client/index.js          # πŸ§ͺ MCP test client (direct & auth modes)
β”œβ”€β”€ cfg/
β”‚   └── roles.json               # πŸ”§ Role-to-tools mapping config
β”œβ”€β”€ iac/
β”‚   β”œβ”€β”€ keycloak/
β”‚   β”‚   └── realm-export.json    # πŸ” Keycloak realm (roles, users, scopes)
β”œβ”€β”€ doc/
β”‚   └── gateway.md               # πŸ“– Full RBAC gateway guide
β”œβ”€β”€ docker-compose.yml           # 🐳 Keycloak + MCP Server + Gateway
β”œβ”€β”€ .env                         # βš™οΈ  Environment configuration
└── .vscode/mcp.json             # πŸ†š VS Code Copilot MCP config

πŸ§ͺ Test Client

The built-in test client implements the full MCP lifecycle and supports both direct and authenticated modes:

# 🟒 Direct β€” no authentication
npm run mcp:client:start

# πŸ”΄ Via Gateway β€” with Keycloak token (uses .env defaults)
npm run mcp:client:gateway

# πŸ”΄ Via Gateway β€” override user from the command line
npm run mcp:client:gateway -- --user mcp-admin --pass admin123

The client runs a diagnostic suite: initialize, ping, list tools, call a tool, list resources, read a resource, and graceful shutdown.


πŸ†š VS Code Copilot Integration

The .vscode/mcp.json file provides two server entries:

Server

URL

Auth

mongodb

http://127.0.0.1:8008/mcp

None

mongodb-gateway

http://127.0.0.1:4040/mcp

Bearer

For mongodb-gateway, VS Code will prompt you to paste a Keycloak access token. Obtain one first (replace user/password as needed):

curl -s -X POST http://localhost:8080/realms/mcp/protocol/openid-connect/token \
  -d "grant_type=password" \
  -d "client_id=mcp-client" \
  -d "username=mcp-admin" \
  -d "password=admin123" \
  -d "scope=openid mcp:access" | node -e "
    let d=''; process.stdin.on('data',c=>d+=c);
    process.stdin.on('end',()=>console.log(JSON.parse(d).access_token));
  "

Copy the token and paste it when VS Code prompts. See doc/gateway.md for more details and all available users.


🐳 Docker Compose

Run the complete stack with a single command:

npm run mcp:docker:start

This starts three services:

Service

Port

Description

keycloak

:8080

πŸ” OAuth 2.1 Authorization Server

mongodb-mcp

:8008

πŸƒ MongoDB MCP Server

mcp-gateway

:4040

πŸ›‘οΈ RBAC Gateway (validates JWT + roles)

Stop everything:

npm run mcp:docker:stop

πŸ“œ npm Scripts

Script

Mode

Description

npm run mcp:wrapper:start

🟒

Start the MCP Server locally

npm run mcp:client:start

🟒

Run diagnostics β€” direct (no auth)

npm run mcp:gateway:start

πŸ”΄

Start the RBAC Gateway locally

npm run mcp:client:gateway

πŸ”΄

Run diagnostics β€” via gateway (with auth)

npm run mcp:client:auth

🟑

Run diagnostics β€” via proxy (with auth)

npm run mcp:docker:start

🐳

Start all Docker services

npm run mcp:docker:stop

🐳

Stop all Docker services


πŸ“– Documentation

Document

Description

doc/gateway.md

πŸ”΄ RBAC Gateway, full guide with Keycloak examples

doc/remote.md

🟒 Securing Remote MongoDB MCP Servers: An RBAC Gateway Architecture


πŸ“š References


πŸ“„ License

ISC

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ameksike/mongodb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server