Ext Ops Panel
Open dashboard
Comparison

Gemini API Docs vs XFMS — Model Source

Gemini API Docs is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). XFMS — Model Source is an MCP server published by xpansion.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceGemini API DocsXFMS — Model Source
Docker MCP Catalog Listed
Version: sha256:ba912546626d
Forks (GitHub): 1
Pulls (Docker Hub): 38 268
Stars (Docker Hub): 2
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.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

Gemini API Docs vs XFMS — Model Source
FactGemini API DocsXFMS — Model Source
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Pulls (Docker Hub) (differs)38 268No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/gemini-api-docs-mcp)Remote server (xfms.vercel.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/kgprs/gemini-api-docs-mcpgithub.com/visionairyse/xfms
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 307 (29 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

Gemini API Docs

In its own words, on Docker MCP Catalog:

Provides tools to search and retrieve Google Gemini API documentation.

XFMS — Model Source

In its own words, on Official MCP Registry:

Pick the right LLM for any task. Ranked shortlist with rationale across 8 evaluators.

How to run each

Gemini API Docs As a local MCP server: Docker image

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

XFMS — Model Source As a remote MCP server

Claude Code
claude mcp add --transport http xfms https://xfms.vercel.app/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only XFMS — Model Source has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of XFMS — Model Source publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Gemini API Docs · What it can do: XFMS — Model Source · Compare two other plugins

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