Ext Ops Panel
Open dashboard
Comparison

Neo — AI/ML Engineering vs Apollo MCP Server

Neo — AI/ML Engineering is an MCP server published by NeoAIResearch. Marketplaces we read that list it: 1 (Official MCP Registry). Apollo MCP Server is an MCP server published by apollographql. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceNeo — AI/ML EngineeringApollo MCP Server
Official MCP Registry Listed
Version: 0.5.5
Downloads/month (PyPI): 1 024
Downloads/week (PyPI): 76
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 2.1.0
Forks (GitHub): 82
Stars (GitHub): 318
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

Neo — AI/ML Engineering vs Apollo MCP Server
FactNeo — AI/ML EngineeringApollo MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)318 (better)
Forks (GitHub) (differs)1 (worse)82 (better)
Last release (differs)Not published2026-10-26
Where it runs (differs)On your machine (neo-mcp)On your machine (ghcr.io/apollographql/apollo-mcp-server:v2.1.0)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/neoairesearch/neo-mcpgithub.com/apollographql/apollo-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Neo — AI/ML Engineering

In its own words, on Official MCP Registry:

AI/ML engineering MCP server for Neo — submit tasks, track execution, and retrieve outputs.

Apollo MCP Server

In its own words, on Official MCP Registry:

MCP server that exposes GraphQL operations as tools for AI models.

How to run each

Neo — AI/ML Engineering As a local MCP server: PyPI package

Claude Code
claude mcp add --env "NEO_SECRET_KEY=<YOUR_NEO_SECRET_KEY>" --transport stdio neo-mcp -- uvx neo-mcp

Requires: NEO_SECRET_KEY (secret)

Apollo MCP Server As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio apollo-mcp-server -- docker run -i --rm --mount "type=bind,src=<YOUR_CONFIG_PATH>,dst=/config.yaml,readonly" --mount "type=bind,src=<YOUR_DATA_PATH>,dst=/data" -p 8000:8000 ghcr.io/apollographql/apollo-mcp-server:v2.1.0 /config.yaml

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

Tools each declares

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

Settings each asks for

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

What it can do: Neo — AI/ML Engineering · What it can do: Apollo MCP Server · Compare two other plugins

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