MongoDB MCP server with optional Mongoose schema support
If you already use Mongo Mongoose MCP, the mongo mongoose mcp mcp server is the piece that lets your assistant work with it directly. MongoDB MCP server with optional Mongoose schema support.
An MCP (Model Context Protocol) server that enables Claude to interact with MongoDB databases, with optional Mongoose schema support.
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
find — Query documents with filtering and projectionlistCollections — List available collectionsinsertOne — Insert a single documentupdateOne — Update a single documentdeleteOne — Soft delete a single documentcount — Count documents with filteringaggregate — Query documents with aggregation pipelinecreateIndex — Create a new indexdropIndex — Remove an indexindexes — List indexes for a collectionConfiguration is passed through the environment: MONGODB_URI, SCHEMA_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mongo Mongoose MCP's toolset — find, listCollections, insertOne and 7 more — is a fair guide to whether it matches your workflow. It is maintained by nabid-pf; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| find | Query documents with filtering and projection |
| listCollections | List available collections |
| insertOne | Insert a single document |
| updateOne | Update a single document |
| deleteOne | Soft delete a single document |
| count | Count documents with filtering |
| aggregate | Query documents with aggregation pipeline |
| createIndex | Create a new index |
| dropIndex | Remove an index |
| indexes | List indexes for a collection |
{
"mcpServers": {
"mongodb-mongoose": {
"command": "npx",
"args": [
"-y",
"mongo-mongoose-mcp",
],
"env": {
"MONGODB_URI": "<your mongodb uri>",
"SCHEMA_PATH" : "<path to the root folder of all your mongoose schema objects>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MONGODB_URI | Configuration value read at startup. | Optional |
| SCHEMA_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.