MongoDB (local)
BetaMongoDB's official server reads and modifies collection data through a connection string.
- Developer Tools
- Local
- Runs
- On the developer's Mac
- Launched with
- npx, Docker
- Platform
- macOS
- Publisher
- MongoDB
How it works
Every agent request passes through Ferentin policy before it reaches MongoDB (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y mongodb-mcp-server or docker run -i --rm mcp/mongodb.
Ferentin's endpoint agent finds MongoDB (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- MongoDB (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About MongoDB (local)
MongoDB's official server reads and modifies collection data through a connection string.
Frequently asked about MongoDB (local)
- How do I connect MongoDB (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add MongoDB (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the MongoDB (local) integration generally available?
- The MongoDB (local) integration is currently beta on Ferentin.
Related integrations
3
Next.js DevTools (local)
Vercel's Next.js DevTools server relays live runtime errors, routes and logs from Next.js development servers to the agent.
Nx (local)
Nx's monorepo server gives the agent the workspace's project graph, file ownership, tasks, code generators and Nx documentation.
Playwright (local)
Microsoft's browser automation server drives a real browser for the agent. It navigates, fills forms, clicks and reads pages.