AgentsReady
Verified deep dive · Observability & auth

MongoDB Atlas

Run the agent liveReport a change
7 minTime to key
NoNo-human path
1Human gates
8/10Onboarding score
Email verification

Fastest path to a key

  1. Zero-account option: `atlas local setup` (Docker) gives a local deployment + connection string with no signup
  2. Email verification
    Cloud: `atlas setup` (or `atlas auth register`/`atlas auth login`) opens browser for signup/login (Google/GitHub or email; email verification), creates a free M0 cluster, DB user and IP access list, and loads sample data
  3. Admin approval
    Connection string returned; for Admin API: create a Service Account (OAuth client credentials) in the org, or let an admin create an MCP Configuration that returns client id/secret + https://mcp.mongodb.com
  4. Working API key

Biggest gap

Remote MCP access is off by default for existing orgs; several auth concepts to learn (App Connections, service accounts, MCP configs, DB users)

Worth copying

Separate MCP access models: user-delegated OAuth vs admin-provisioned MCP Configurations with ingress/egress service accounts, so egress creds are never exposed to the agent

Sources (8) · checked 2026-10-11
72Readiness score / 100
L3 Agent-operableBeats 90% of 1,846 companies
Access20/20
Context17/20
Interfaces24/32
Onboarding8/19
Trust3/9
llms.txt · root
MCP · https://mcp.mongodb.com/mcp

Biggest gains

  1. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
  2. +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
  3. +5 Self-serve API keys. Show how to create a key on the first docs page. No sales call.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • FAILAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • PASSFree tier or test mode3
  • FAILAgent manifests4
  • FAILsecurity.txt2
  • PASSPublic status page3

Your fix pack: 7 changes, up to +28 points

Each change is ready to paste, filled in for mongodb.com, with a command to check it worked. Or hand the whole list to your coding agent.

An OpenAPI spec is the contract agents and SDK generators build against. Without it they guess from prose.

Where: https://mongodb.com/openapi.json, linked from llms.txt and the API reference
// Serve the spec your API framework already generates (FastAPI: /openapi.json is built in).
// Next.js: app/openapi.json/route.ts
import spec from "@/openapi/openapi.json";
export const GET = () => Response.json(spec, { headers: { "Access-Control-Allow-Origin": "*" } });

// Every operation needs: operationId, summary, description, request/response examples,
// and the auth scheme (components.securitySchemes) so agents know how to send the key.
Check it worked:curl -s https://mongodb.com/openapi.json | head -c 200

Add the badge to your README

AgentsReady badge for mongodb.com
[![AgentsReady](https://agentsready.dev/badge/mongodb.com)](https://agentsready.dev/c/mongodb.com)