MongoDB MCP Server
Servidor MCP de MongoDB
Un servidor de protocolo de contexto de modelo que proporciona acceso de solo lectura a las bases de datos MongoDB a través de herramientas y recursos MCP estandarizados.
Descripción general
Este servidor MongoDB MCP permite a los asistentes de IA consultar y analizar directamente bases de datos MongoDB sin acceso de escritura, manteniendo la seguridad de los datos y proporcionando potentes capacidades de exploración de datos.
Related MCP server: MongoDB MCP Server for LLMs
Características
Operaciones de MongoDB
Exploración de bases de datos : enumerar bases de datos y colecciones
Descubrimiento de esquemas : inferir esquemas de colección a partir de documentos de muestra
Consultas : Ejecute consultas MongoDB con filtrado, proyección, ordenación y limitación.
Agregación : ejecute canales de agregación de solo lectura con validación de seguridad
Búsqueda de texto : realice una búsqueda de texto completo en colecciones con índices de texto
Consultas geoespaciales : encuentre ubicaciones cerca de puntos, dentro de polígonos o geometrías que se intersecan
Operaciones con documentos : contar documentos, tomar muestras aleatorias de documentos, buscar documentos por ID
Análisis de datos : obtenga estadísticas de recopilación, información de índices y planes de ejecución de consultas
Información sobre el rendimiento : examine los planes de ejecución de consultas para optimizar el rendimiento
Exploración de datos : obtenga valores distintos, distribuciones de campos y muestras de datos
Conversión de formato : Exportar resultados de consultas en formatos JSON o CSV
Capacidades mejoradas
Inferencia de esquemas : detecta automáticamente los tipos de datos y la estructura de los documentos
Sugerencias de visualización : sugerencias inteligentes para la visualización de datos basadas en el contenido de los resultados
Validación de seguridad : evita operaciones de escritura en canales de agregación
Documentación rica en ejemplos : cada herramienta incluye ejemplos detallados en su descripción
Requisitos
Variables de entorno
MONGODB_URI(obligatorio): cadena de conexión de MongoDB con autenticación si es necesarioMONGODB_DEFAULT_DATABASE(opcional): nombre de base de datos predeterminado cuando no se especifica en las consultas
Prerrequisitos
Acceso de red al servidor MongoDB
Credenciales de autenticación si la instancia de MongoDB lo requiere
Permisos de lectura adecuados en las bases de datos de destino
Instalación
Construyendo desde la fuente
Instalar dependencias:
npm installConstruir el servidor:
npm run buildPara desarrollo con reconstrucción automática:
npm run watchIntegración con Claude Desktop
Para utilizar con Claude Desktop, agregue la configuración del servidor:
En MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json En Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"mongodb": {
"command": "/path/to/mongodb-server/build/index.js",
"env": {
"MONGODB_URI": "mongodb://username:password@hostname:port/database",
"MONGODB_DEFAULT_DATABASE": "your_default_db"
}
}
}
}Integración con Claude Web
Para Claude Web a través de la extensión MCP de Chrome, agregue la configuración a la configuración de Cline MCP:
{
"mcpServers": {
"mongodb": {
"command": "node",
"args": ["/path/to/mongodb-server/build/index.js"],
"env": {
"MONGODB_URI": "mongodb://username:password@hostname:port/database",
"MONGODB_DEFAULT_DATABASE": "your_default_db"
}
}
}
}Integración con Claude Code
Para utilizar con Claude Code, utilice los siguientes comandos:
cd /path/to/my/project
claude mcp add mongo-server /path/to/mongodb-mcp/build/index.js -e "MONGODB_URI=mongodb://user@password:27017/dbname?authSource=authDbName" -e MONGO_DEFAULT_DATABASE=dbname Asegúrese de reemplazar los marcadores de posición con la cadena de conexión MongoDB real y el nombre de la base de datos predeterminada.
Si está configurado correctamente, debería ver lo siguiente cuando ejecute claude :
╭───────────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code research preview! │
│ │
│ /help for help │
│ │
│ cwd: <path-to-project-directory> │
│ │
│ ─────────────────────────────────────────────────── │
│ │
│ MCP Servers: │
│ │
│ • mongo-server connected │
╰───────────────────────────────────────────────────────╯
Si tiene algún problema, consulte la documentación de Claude Code.
Consideraciones de seguridad
Este servidor proporciona acceso de solo lectura por diseño.
Las cadenas de conexión pueden contener información de autenticación confidencial
Almacenar cadenas de conexión de forma segura en variables de entorno
Utilice un usuario MongoDB con permisos de solo lectura
Depuración
Dado que los servidores MCP se comunican a través de stdio, la depuración puede ser complicada. Utilice el Inspector MCP , disponible como script de paquete:
npm run inspectorEl Inspector proporcionará una URL para acceder a las herramientas de depuración en su navegador.
Available Tools
14 toolsaggregateA
Execute a read-only aggregation pipeline on a collection.
Supported Stages:
$match: Filter documents
$group: Group documents by a key
$sort: Sort documents
$project: Shape the output
$addFields - Include additional or calculated fields
$lookup: Perform left outer joins
$unwind: Deconstruct array fields
Unsafe/Blocked Stages:
$out: Write results to collection
$merge: Merge results into collection
$set: Set field values
$unset: Remove fields
$replaceRoot: Replace document structure
$replaceWith: Replace document
Example - User Statistics by Role: use_mcp_tool with server_name: "mongodb", tool_name: "aggregate", arguments: { "collection": "users", "pipeline": [ { "$match": { "active": true } }, { "$group": { "_id": "$role", "count": { "$sum": 1 }, "avgAge": { "$avg": "$age" } }}, { "$sort": { "count": -1 } } ], "limit": 100 }
Example - Posts with Author Details: use_mcp_tool with server_name: "mongodb", tool_name: "aggregate", arguments: { "collection": "posts", "pipeline": [ { "$match": { "published": true } }, { "$lookup": { "from": "users", "localField": "authorId", "foreignField": "_id", "as": "author" }}, { "$unwind": "$author" }, { "$project": { "title": 1, "authorName": "$author.name", "publishDate": 1 }} ] }
Inputs: collection (required), pipeline (required), database, limit.
count_documentsA
Count documents in a collection that match a filter.
Benefits:
More efficient than retrieving full documents
Good for understanding data volume
Can help planning query strategies
Optimize pagination implementation
Example: use_mcp_tool with server_name: "mongodb", tool_name: "count_documents", arguments: { "collection": "users", "filter": { "active": true, "age": { "$gte": 21 } } }
Inputs: collection (required), database, filter.
explain_queryA
Get the execution plan for a query.
Helps understand:
How MongoDB will execute the query
Which indexes will be used
Number of documents examined
Execution stages and timing
Use this to optimize slow queries.
Inputs: collection (required), filter (required), database, projection, +1 more.
find_by_idsA
Find multiple documents by their IDs in a single request.
Advantages:
More efficient than multiple single document lookups
Preserves ID order in results when possible
Can filter specific fields with projection
Handles both string and ObjectId identifiers
Example: use_mcp_tool with server_name: "mongodb", tool_name: "find_by_ids", arguments: { "collection": "products", "ids": ["5f8d0f3c", "5f8d0f3d", "5f8d0f3e"], "idField": "_id", "projection": { "name": 1, "price": 1 } }
Inputs: collection (required), ids (required), database, idField, +1 more.
geo_queryA
Execute geospatial queries on a MongoDB collection.
Supports:
Finding points near a location
Finding documents within a polygon, circle, or box
Calculating distances between points
GeoJSON and legacy coordinate pair formats
Requirements:
Collection must have a geospatial index (2dsphere recommended)
Coordinates should follow MongoDB conventions (longitude first, then latitude)
Examples:
Find locations near a point (2 miles radius): use_mcp_tool with server_name: "mongodb", tool_name: "geo_query", arguments: { "collection": "restaurants", "operation": "near", "point": [-73.9667, 40.78], "maxDistance": 3218.69, // 2 miles in meters "distanceField": "distance" }
Find locations within a polygon: use_mcp_tool with server_name: "mongodb", tool_name: "geo_query", arguments: { "collection": "properties", "operation": "geoWithin", "geometry": { "type": "Polygon", "coordinates": [ [[-73.958, 40.8], [-73.94, 40.79], [-73.95, 40.76], [-73.97, 40.76], [-73.958, 40.8]] ] } }
Inputs: collection (required), operation (required), database, locationField, +8 more.
get_collection_statsC
Get detailed statistics about a collection.
Returns information about:
Document count and size
Storage metrics
Index sizes and usage
Average document size
Padding factor
Inputs: collection (required), database.
get_distinct_valuesA
Get distinct values for a field in a collection.
Useful for:
Understanding data distribution
Finding unique categories
Data quality checks
Identifying outliers
Example: use_mcp_tool with server_name: "mongodb", tool_name: "get_distinct_values", arguments: { "collection": "users", "field": "role", "filter": { "active": true } }
Inputs: collection (required), field (required), database, filter.
get_indexesB
Get information about indexes on a collection.
Returns details about:
Index names and fields
Index types (single field, compound, text, etc.)
Index sizes
Index options
Usage statistics
Inputs: collection (required), database.
get_schemaA
Infer schema from a collection by analyzing sample documents.
Best Practice: Use this before querying to understand collection structure.
Example: use_mcp_tool with server_name: "mongodb", tool_name: "get_schema", arguments: { "collection": "users", "sampleSize": 100 }
Inputs: collection (required), database, sampleSize.
list_collectionsA
List all collections in a database.
Start here to understand what collections are available before querying.
Inputs: database.
list_databasesB
List all databases in the MongoDB server.
Inputs: no named parameters.
queryA
Execute a read-only query on a collection using MongoDB query syntax.
Supports both JSON and CSV output formats:
Use outputFormat="json" for standard JSON (default)
Use outputFormat="csv" for comma-separated values export
Best Practices:
Use projections to fetch only needed fields
Add limits for large collections
Use sort for consistent ordering
Example - Standard Query: use_mcp_tool with server_name: "mongodb", tool_name: "query", arguments: { "collection": "users", "filter": { "age": { "$gte": 21 } }, "projection": { "name": 1, "email": 1 }, "sort": { "name": 1 }, "limit": 100 }
Example - CSV Export: use_mcp_tool with server_name: "mongodb", tool_name: "query", arguments: { "collection": "users", "filter": { "active": true }, "outputFormat": "csv", "formatOptions": { "includeHeaders": true, "delimiter": "," } }
Inputs: collection (required), filter (required), database, projection, +4 more.
sample_dataA
Get a random sample of documents from a collection.
Supports both JSON and CSV output formats:
Use outputFormat="json" for standard JSON (default)
Use outputFormat="csv" for comma-separated values export
Useful for:
Exploratory data analysis
Testing with representative data
Understanding data distribution
Performance testing with realistic data subsets
Example - JSON Sample: use_mcp_tool with server_name: "mongodb", tool_name: "sample_data", arguments: { "collection": "users", "size": 50 }
Example - CSV Export: use_mcp_tool with server_name: "mongodb", tool_name: "sample_data", arguments: { "collection": "users", "size": 100, "outputFormat": "csv", "formatOptions": { "includeHeaders": true, "delimiter": "," } }
Inputs: collection (required), database, size, outputFormat, +1 more.
text_searchB
Perform a full-text search on a collection.
Requirements:
Collection must have a text index
Only one text index per collection is allowed
Features:
Supports phrases and keywords
Word stemming
Stop words removal
Text score ranking
Example: use_mcp_tool with server_name: "mongodb", tool_name: "text_search", arguments: { "collection": "articles", "searchText": "mongodb database", "filter": { "published": true }, "limit": 10, "includeScore": true }
Inputs: collection (required), searchText (required), database, filter, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools have distinct purposes, such as aggregate for complex pipelines, query for basic queries, and geo_query for spatial operations. However, query and sample_data both retrieve documents with overlapping functionality, and get_schema might be confused with get_collection_stats for understanding collection structure, leading to some potential confusion.
The naming follows a consistent verb_noun pattern throughout, like count_documents, explain_query, and get_indexes. There are minor deviations with list_collections and list_databases using 'list' instead of 'get', but overall the pattern is clear and predictable.
With 14 tools, this is well-scoped for a MongoDB server, covering a comprehensive range of read-only operations from basic queries to advanced analytics. Each tool serves a specific purpose, such as aggregation, indexing, geospatial queries, and schema analysis, without feeling bloated or incomplete.
The tool set provides complete coverage for read-only MongoDB operations, including querying, aggregation, indexing, geospatial queries, text search, and metadata inspection. There are no obvious gaps; it supports everything from data retrieval to performance optimization and schema exploration for the domain.
Maintenance
Related MCP Connectors
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
Query your org's data in natural language — read-only MCP access to SQL, NoSQL, files & warehouses.
The BigQuery remote MCP server is a fully managed service that uses the Model Context Protocol to connect AI applications and LLMs to BigQuery data sources. It provides secure, standardized tools for AI agents to list datasets and tables, retrieve schemas, generate and execute SQL queries through natural language, and analyze data—enabling direct access to enterprise analytics data without requiring manual SQL coding.
Draxlr's remote MCP server connects AI assistants to your SQL databases and dashboards. Explore schemas, run read-only queries, manage saved queries and dashboards, and export results, all with row-level security so each user sees only their own data.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact directly with MongoDB databases, allowing users to query collections, inspect schemas, and manage data through natural language.1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact directly with MongoDB databases, allowing users to query collections, inspect schemas, and manage data through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for MongoDB operations, enabling AI assistants to interact with MongoDB databases through a standardized interface.6MIT
- FlicenseNot gradedqualityDmaintenanceA read-only MongoDB MCP server designed for serverless deployment on Vercel, providing secure, limited access to MongoDB databases for AI assistants.1-