mongodb-mcp-setup
Guide users through configuring key MongoDB MCP server options. Use this skill when a user has the MongoDB MCP server installed but hasn't configured the required environment variables, or when they ask about connecting to MongoDB/Atlas and don't have the credentials set up.
npx skills add fcakyon/claude-codex-settings --skill mongodb-mcp-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MongoDB MCP Server Setup This skill guides users through configuring the MongoDB MCP server for use with an agentic client. ## Overview The MongoDB MCP server requires authentication. Users have three options: 1. **Connection String** (Option A): Direct connection to a specific cluster - Quick setup for single cluster - Requires `MDB_MCP_CONNECTION_STRING` environment variable 2. **Service Account Credentials** (Option B): MongoDB Atlas Admin API access - **Recommended for Atlas users** - simplifies authentication and data access - Access to Atlas Admin API and dynamic cluster connection via `atlas-connect-cluster` - No manual DB user credential management - Requires `MDB_MCP_API_CLIENT_ID` and `MDB_MCP_API_CLIENT_SECRET` environment variables 3. **Atlas Local** (Option C): Local development with Docker - **Best for local testing** - zero configuration required - Runs Atlas locally in Docker, requires Docker installed - No credentials or cloud cluster access This is an interactive step-by-step guide. The agent detects the user's environment and provides tailored instructions, but **never asks for or handles credentials** — users add those directly to their shell profile or agenti
- Overview
- Step 0: Detect Client
- Step 1: Check Existing Configuration
- Step 2: Present Configuration Options
- Step 3a: Connection String Setup
- 3a.1: Explain How to Find the Connection String
- Step 3b: Service Account Setup
- 3b.1: Guide Through Atlas Service Account Creation
- 3b.2: API Access List Configuration
- Step 3c: Atlas Local Setup
- 3c.1: Check Docker Installation
- 3c.2: Confirm Setup Complete
- Step 4: Determine Read-Only vs Read-Write Access
- Step 5: Configure Credentials
env | grep "^CODEX_" env | grep "^MDB_MCP" | sed '/^MDB_MCP_READ_ONLY=/!s/=.*/=[set]/' docker info export MDB_MCP_CONNECTION_STRING="<paste-your-connection-string-here>" export MDB_MCP_API_CLIENT_ID="<paste-your-client-id-here>" export MDB_MCP_API_CLIENT_SECRET="<paste-your-client-secret-here>" adjust for windows if needed chmod 600 ~/.mcp-env source ~/.zshrc # adjust to match the profile file adjust path if on Windows
What does the mongodb-mcp-setup skill do?
Guide users through configuring key MongoDB MCP server options. Use this skill when a user has the MongoDB MCP server installed but hasn't configured the required environment variables, or when they ask about connecting to MongoDB/Atlas and don't have the credentials set up.
How do I install it?
Run `npx skills add fcakyon/claude-codex-settings --skill mongodb-mcp-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From fcakyon/claude-codex-settings, a repository with 967 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.