Ext Ops Panel
Open dashboard
Comparison

Atlas Docs vs Javadocs

Atlas Docs is an MCP server published by CartographAI. Marketplaces we read that list it: 1 (Docker MCP Catalog). Javadocs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-13. 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
MarketplaceAtlas DocsJavadocs
Docker MCP Catalog Listed
Version: sha256:4d235adb7498
Forks (GitHub): 5
Pulls (Docker Hub): 24 109
Stars (Docker Hub): 2
Stars (GitHub): 36
Not marked · First seen
Listed
Version: not stated
No figure published
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

Atlas Docs vs Javadocs
FactAtlas DocsJavadocs
Marketplaces that list it11
Stars (GitHub) (differs)36No figure on GitHub
Pulls (Docker Hub) (differs)24 109No figure on Docker Hub
Forks (GitHub) (differs)5No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/atlas-docs)Remote server (www.javadocs.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)58
Environment variables it asks for (differs)1, secrets among them: 0Not published
Licence (differs)MITApache-2.0
Repository (differs)github.com/cartographai/atlas-docs-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

Atlas Docs

In its own words, on Docker MCP Catalog:

Provide LLMs hosted, clean markdown documentation of libraries and frameworks.

Javadocs

In its own words, on Docker MCP Catalog:

Access to Java, Kotlin, and Scala library documentation.

How to run each

Atlas Docs As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio atlas-docs -- docker run -i --rm mcp/atlas-docs

Javadocs As a remote MCP server

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

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

Tools each declares

Only Atlas Docs declares

  • get_docs_full
  • get_docs_index
  • get_docs_page
  • list_docs
  • search_docs

Only Javadocs declares

  • get_javadoc_index
  • get_javadoc_symbol
  • get_latest_version
  • get_source_file
  • list_javadoc_symbols
  • list_source_files
  • search_artifacts
  • symbol_to_artifact

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of Javadocs publish no settings it asks for, so we do not compare settings.

What it can do: Atlas Docs · What it can do: Javadocs · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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