Ext Ops Panel
Open dashboard
Comparison

code-atlas-mcp vs Context Atlas

code-atlas-mcp is an MCP server published by SerPeter. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Context Atlas is an MCP server published by levin-staudt. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecode-atlas-mcpContext Atlas
PyPI (MCP servers) Listed
Version: 0.15.5
Downloads/month (PyPI): 762
Downloads/week (PyPI): 130
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

code-atlas-mcp vs Context Atlas
Factcode-atlas-mcpContext Atlas
Marketplaces that list it11
Stars (GitHub) (differs)7 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)2026-10-23Not published
Where it runs (differs)On your machine (code-atlas-mcp)Remote server (contextatlas.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/serpeter/code-atlasgithub.com/levin-staudt/contextatlas
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-23
Endpoint at the last check (differs)no remote endpoint we checkResponded 7 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

code-atlas-mcp

In its own words, on PyPI (MCP servers):

A code intelligence graph that gives AI coding agents deep, token-efficient understanding of your codebase.

Context Atlas

In its own words, on Official MCP Registry:

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

How to run each

code-atlas-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Context Atlas As a remote MCP server

Claude Code
claude mcp add --transport http contextatlas https://contextatlas.dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Context Atlas has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: code-atlas-mcp · What it can do: Context Atlas · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built