io.github.AceDataCloud/mcp-openai vs io.github.Hebline/mcp-server
io.github.AceDataCloud/mcp-openai is an MCP server published by AceDataCloud. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Hebline/mcp-server is an MCP server published by Hebline. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  io.github.AceDataCloud/mcp-openai |  io.github.Hebline/mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 2026.10.19.5 Downloads/month (PyPI): 388 Downloads/week (PyPI): 985 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.2.1 Downloads/month (npm): 202 Downloads/week (npm): 42 Forks (GitHub): 0 Stars (GitHub): 1 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 | io.github.AceDataCloud/mcp-openai | io.github.Hebline/mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (@hebline.ai/mcp-server) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 3 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/acedatacloud/openaimcp | github.com/hebline/mcp-server |
| Changes in the last 7 days (differs) | 19 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | no remote endpoint we check |
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
io.github.AceDataCloud/mcp-openai
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
io.github.Hebline/mcp-server
Intelligent API routing for AI agents. Best service, best price, free alternatives.
How to run each
io.github.AceDataCloud/mcp-openai As a remote MCP server
claude mcp add --transport http mcp-openai https://openai.mcp.acedata.cloud/mcpRequires: ACEDATACLOUD_API_TOKEN (secret)
io.github.Hebline/mcp-server As a local MCP server: npm package
claude mcp add --env "DEEPL_API_KEY=<YOUR_DEEPL_API_KEY>" --env "GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>" --env "LIBRETRANSLATE_API_KEY=<YOUR_LIBRETRANSLATE_API_KEY>" --transport stdio io-github-hebline-mcp-server -- npx -y @hebline.ai/mcp-serverRequires: DEEPL_API_KEY (secret), GOOGLE_MAPS_API_KEY (secret), LIBRETRANSLATE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.AceDataCloud/mcp-openai 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
Only io.github.AceDataCloud/mcp-openai asks for
ACEDATACLOUD_API_TOKEN (secret)
Only io.github.Hebline/mcp-server asks for
DEEPL_API_KEY (secret)GOOGLE_MAPS_API_KEY (secret)LIBRETRANSLATE_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.AceDataCloud/mcp-openai · What it can do: io.github.Hebline/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.