Context Atlas

io.github.levin-staudtPublished by GitHub account levin-staudtv1.0.0Updated Oct 24, 2026

Find llms.txt, docs, MCP servers, skills and CLIs for a tech stack, for coding agents.

The publisher's own server: Red Atlas Api

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A remote MCP server that catalogs the llms.txt files, docs, MCP servers, skills, rules and CLIs vendors publish for coding agents, searchable by tool or stack.

What you can do
Search the catalog by tool name, role, region or detection signal such as files, dependencies and environment variables, with prefix matching on every word. Retrieve one tool's full source list, detection signals and role by its id. List every cataloged tool with id, name, role and region to find candidates per role. Compare tools by following their llms.txt or rules sources.
When to use it
Useful when a coding assistant needs to find the right agent-facing sources for an existing tech stack, or wants to compare candidate tools by role before proposing a stack for a new project.
Requirements
A remote Streamable HTTP endpoint; no package, account, API key or environment variable is declared. Network access to the service is needed.
Before you install
The catalog only links to vendor sources; content belongs to each vendor and should be checked at the source. Full-text sources are several megabytes, so the server advises fetching a topic's llms.txt or rules first. The server is read-only and stateless.

Installation

In SourceWeft

  1. Open Context Atlas in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.levin-staudt%2Fcontextatlas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "context-atlas": {
      "type": "http",
      "url": "https://contextatlas.dev/mcp"
    }
  }
}

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.

bash
bun installbun dev          # http://localhost:3000, hot reload for the pages, restart on server changesbun run check    # lint, typecheck, tests: run before every commitbun 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.

Source: README.md at commit 97845e8

Tools

3

get_topic

Get a topic

All sources (llms.txt, docs, MCP servers, skills, rules), detection signals and the role of one tool, by id such as `vercel`, `nextjs` or `drizzle`.

Parametersidrequired

list_topics

List topics

Every tool in the catalog with its id, name, role and region, without sources. Use it to find candidates per role, then get_topic and their llms.txt sources to compare them.

Parametersregion

Version history

1
  1. v1.0.0LatestOct 24, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Atlas integrations