mongodb.com
MongoDB exposes two documented HTTP APIs (Atlas Administration API and Atlas App Services Admin API), an Atlas CLI plus legacy `mongocli`, and an official MongoDB MCP server; authentication is required via Atlas service-account OAuth client credentials, legacy Atlas API key pairs, or an App Services bearer session token minted from Atlas API keys.
- MongoDB MCP Serverdiscovered
- MongoDB Atlas Administration APIdiscovered
- MongoDB Atlas App Services Admin APIdiscovered
- Atlas CLIdiscovered
- MongoDB CLI (mongocli)discovered
In Get Started with the Atlas Administration API, go to Applications in your Atlas organization, click Add new Service Account, assign organization/project roles, create it, and copy the client secret when shown. Use the client ID and secret to mint an OAuth token with the client-credentials flow at POST https://cloud.mongodb.com/api/oauth/token.
$ atlas auth loginAcquired by the CLI — running atlas auth login opens the auth flow and stores the credential.
First create Atlas programmatic API keys using Get Started with the Atlas Administration API. Then call the App Services admin login endpoint described in MongoDB Atlas App Services Admin API with JSON {"username":"<Public API Key>","apiKey":"<Private API Key>"} at POST https://services.cloud.mongodb.com/api/admin/v3.0/auth/providers/mongodb-cloud/login to receive an access_token. Use the returned refresh_token with POST https://services.cloud.mongodb.com/api/admin/v3.0/auth/session to renew it.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://mongodb.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing