mcpField
C
Context Atlas

Context Atlas

Remote
contextatlas.devDeveloper Tools0Updated 4d ago

About Context Atlas

Context Atlas is a catalog for coding agents and developers to find vendor-published documentation, llms.txt indexes, MCP servers, skills, rules, and CLIs by technology stack. It combines searchable listings with topic-specific sources and a stateless MCP server.

Key features

  1. 01Search sources by kind and topic
  2. 02Catalog docs, MCP servers, skills, and CLIs
  3. 03Provide stack-specific agent prompts
  4. 04Serve topic data as text and JSON
  5. 05Stateless MCP search and topic tools

Use cases

  1. 01Find documentation for an existing tech stack
  2. 02Locate MCP servers or skills for a project
  3. 03Explore sources when proposing a new stack

MCP support

The stateless Streamable HTTP MCP server provides `search`, `get_topic`, and `list_topics` tools for querying the catalog.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://contextatlas.dev/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Context Atlas

Live: https://contextatlas.dev (the old https://contextatlas.levinstaudt.workers.dev redirects there with a 301)

Chart a tech stack, or find the right sources for the one you have. Context Atlas collects the llms.txt indexes, docs, MCP servers, agent skills, rule files and CLIs that vendors publish for coding agents, grouped into cloud providers, frameworks, standards and CLIs.

The site only links to the sources; every source belongs to its vendor.

  • / lists every source, filterable by search and by kind (the map legend).
  • /agent has a copy button for a one-sentence prompt, either for an existing project (detect the stack, then follow the matching sources) or for a new one (propose a stack), and the command to add the MCP server.
  • /llms.txt holds the agent instructions and the full catalog; the prompt only links to it. /atlas.json has the same data as JSON.
  • /llms/<topic-id>.txt holds a single topic, for agents that need only one tool's sources.
  • /mcp is a stateless MCP server (Streamable HTTP) with the tools search, get_topic and list_topics: claude mcp add --transport http contextatlas https://contextatlas.dev/mcp.
  • /api/topics, /api/topics/<id> and /api/search?q=<words>&kind=<kind>&limit=<n> are the JSON API for the CLI (#13).

Add a source

All content lives in packages/core/src/catalog.ts. Add a Source to an existing topic, or a new Topic with a role and signals (how an agent detects it in a repo: file(...), dep(...), env(...) or hint(...)). Bump updatedAt. Then run bun run check; the catalog tests catch duplicate ids, bad URLs and malformed signals. The add-source skill has the details.

Everything the site serves is read from SQLite, which bun run seed (and every deploy) rebuilds from that file.

Develop

Bun workspaces, Hono in front for the agent files, the API and MCP, React Router (framework mode, server-rendered, Vite) for the pages, SQLite through Drizzle with FTS5 search, the MCP TypeScript SDK and Tailwind CSS.

bun install
bun dev          # http://localhost:3000, hot reload for the pages, restart on server changes
bun run check    # lint, typecheck, tests: run before every commit
bun run build    # dist/: single binary (server + pages) + public/ + drizzle/
bun run deploy   # deploy main to the VPS through GitHub Actions
PathWhat
packages/coreCatalog, database schema and migrations, seed, queries, search, llms.txt text. Transport-free.
apps/serverHono app: agent files, JSON API, MCP, static files; hands every other path to apps/web. src/main.ts is the binary (seed, serve), src/dev.ts the dev server.
apps/webThe pages for people: React Router routes, components and styles. Reads the catalog from the server's snapshot, no data logic. See docs/web-frontend.md.
apps/redirectCloudflare Worker that 301s the old workers.dev URL to the new domain.
deploy/systemd unit and VPS scripts.
scripts/Cloudflare setup, VPS access, IndexNow ping and the share image, all from the harness.
server.json, glama.jsonThe remote MCP server's entries for the official MCP Registry and Glama.
docs/deploy.mdInfrastructure and runbook.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.