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
| Marketplace | ||
|---|---|---|
| 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
| Fact | Atlas Docs | Javadocs |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 36 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 24 109 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/atlas-docs) | Remote server (www.javadocs.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 5 | 8 |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/cartographai/atlas-docs-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not 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
Provide LLMs hosted, clean markdown documentation of libraries and frameworks.
Javadocs
Access to Java, Kotlin, and Scala library documentation.
How to run each
Atlas Docs As a local MCP server: Docker image
claude mcp add --transport stdio atlas-docs -- docker run -i --rm mcp/atlas-docs
Javadocs As a remote MCP server
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_fullget_docs_indexget_docs_pagelist_docssearch_docs
Only Javadocs declares
get_javadoc_indexget_javadoc_symbolget_latest_versionget_source_filelist_javadoc_symbolslist_source_filessearch_artifactssymbol_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.