MongoDB
MongoDB hosts the Atlas Managed MCP server at https://mcp.mongodb.com. It covers Atlas clusters only. Self-managed MongoDB needs a server you run yourself. The Official card uses client credentials from an Atlas MCP configuration, not a person's Atlas login. An Organization Owner or Project Owner creates that configuration. The agent then acts as the configuration's service account, with the Atlas roles you assign. It is the MongoDB card with the Official badge. Willow also has a built-in MongoDB connector.
Atlas also offers user-delegated OAuth (AI Clients). That is a different access model. This card is the programmatic one.
Set up Atlas
- An organization owner enables AI Clients if your project requires it before MCP configurations can be created.
- Create an MCP configuration. Name it, for example
Willow. - Pick at least one Atlas role. Read-only is the default. A role with write access applies across the project.
- Optionally restrict source IPs and set how long the client secret stays valid.
- Copy the Client ID and Client Secret. Atlas shows the secret once.
Set up Willow
- Go to MCP Servers → + Add MCP server, open the MongoDB card with the Official badge, and click + Use.
- Keep Client credentials. Paste the Client ID and Client Secret from the MCP configuration.
- Click Check connection. Assign groups and Publish.
Calls are attributed to the configuration's service account, not to the Willow user who triggered them.
Troubleshooting
The client cannot register itself
Cause: Atlas does not support dynamic client registration for this server.
Solution: Create the MCP configuration in Atlas and paste its client ID and secret. A regular Atlas service account is not the same credential.