all-mcp — One MCP Server for All of Them
One MCP server containing all 60 of Mohammad Abbasi's MCP servers — Turkey (32), Germany (27), Bonbama (1) — 324 tools behind a single config entry. Ask anything; it connects to the right MCP itself.
Ask in Persian, Turkish, German, or English:
«قیمت بلیط قطار از برلین به مونیخ چقدره؟» → finds
flixtrain_search_trains, calls it, returns real departures and prices.
«قیمت اتوبوس مونیخ به هامبورگ» → routes to Germany transport, not Turkey — because the question names German cities.
How it actually works (honest version)
There is no magic detection inside this server. By default, your own AI — Claude Desktop, Claude Code, Cursor — does the detecting:
search_tools(query)— keyword search over all 324 tools in all four languages, ranked by topic match, place match (cities/countries named in the question), and your saved location. Returns the best tools with server, country, and a one-line description.call_tool(server, tool, arguments)— runs the chosen tool on the right child server (spawned on demand viauvx) and returns its real result.
Exposing all 324 tools at once would drown any client (context blowup, wrong picks). So the router exposes only 6 tools — the standard router pattern:
| Tool | What it does |
|---|---|
search_tools(query, limit?) |
Ranked tools for a question (any language) |
call_tool(server, tool, arguments?, timeout?) |
Run one tool on one child server |
ask(question, location?) |
One-step answer: route + run + explain (see below) |
list_servers(catalog?, country?, category?) |
Browse the 60 servers |
set_location(country, city?) |
Save your country for location-first routing (local file only) |
meta_health() |
Index counts, PyPI status, uvx, current location, routing provider |
One search + one call — no extra round trips. Or one ask — see next section.
ask: one-step answers (optional routing LLM)
ask(question) answers in a single call: it routes the question to the right server+tool+arguments, executes it, and returns the result plus a one-line routing explanation, alternatives, a routing trace (steps: one entry per routing/execution attempt, {server, tool, status, ms}), and citation links (sources).
Routing needs a small LLM. It uses your own key (or a local model) — the router never ships a key, and the key never leaves your machine except to the provider you chose:
| Provider | Env var | Default model | Free? |
|---|---|---|---|
| Gemini | GEMINI_API_KEY |
gemini-3.5-flash |
Free tier at AI Studio |
| OpenAI | OPENAI_API_KEY |
gpt-4o-mini |
Paid |
| Anthropic | ANTHROPIC_API_KEY |
claude-haiku-4-5 |
Paid |
| OpenRouter | OPENROUTER_API_KEY |
nvidia/nemotron-3.5-lightning:free |
Free-tier models — good default with no paid key |
| Ollama (local) | — | qwen2.5:7b |
Fully free/local, no key at all |
Selection: LLM_PROVIDER env override (gemini / openai / anthropic / openrouter / ollama), else the first configured provider in that order. Ollama is only used when explicitly selected (LLM_PROVIDER=ollama, host http://localhost:11434 by default; ollama pull qwen2.5:7b first). Model overrides: ALL_MCP_<PROVIDER>_MODEL (e.g. ALL_MCP_GEMINI_MODEL).
No provider at all? ask still works: it falls back to the top search result — auto-executed when it needs no arguments, otherwise returned with the required parameters listed. search_tools + call_tool always work with no key at all.
HTTP bridge: the website chat UI
The site's chat talks to the router running on your own machine (local bridge — still no backend of ours):
uvx all-mcp --http --port 8765
Localhost-only (127.0.0.1). Endpoints:
| Endpoint | Body | Returns |
|---|---|---|
GET /api/health |
— | servers/tools indexed, LLM configured yes/no (never the key) |
POST /api/search |
{"query", "limit"?} |
ranked tools |
POST /api/call |
{"server", "tool", "arguments"?} |
the tool result |
POST /api/ask |
{"question", "location"?} |
one-step answer + steps + sources |
curl -X POST http://127.0.0.1:8765/api/ask \
-H 'Content-Type: application/json' \
-d '{"question": "قیمت بلیط قطار از برلین به مونیخ چقدره؟"}'
CORS allows only https://mohammad-abbasi-sh.github.io and localhost origins. /api/ask accepts an optional per-request location hint ({"country": "DE", "city": "Berlin"}) sent by the chat UI from its browser memory — it beats the saved location, and explicit place names in the question still beat it. The response's steps array is the live routing trace the chat UI animates ("connecting to flixtrain-mcp…"), and sources are the citation links.
Install (one config entry)
Requires uvx (install uv). Add to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"all-mcp": {
"command": "uvx",
"args": ["all-mcp"],
"env": {
"USER_COUNTRY": "DE"
}
}
}
}
USER_COUNTRY is optional (DE / TR / IR): it tells the router where you are, so an ambiguous question with no place names routes to your country's services. Set it once at install. Without it, use the set_location tool (saved to ~/.config/all-mcp/location.json on your machine only).
Then just ask questions. Try: «هوای برلین چطوره؟», «dollar exchange rate today», «Fußball Ergebnisse Bundesliga», «تخفیف گرگان».
Ranking priority
- Explicit place names in the question win. «اتوبوس مونیخ به هامبورگ» routes to Germany even if your saved location is Turkey.
- A per-request location hint beats the saved location. The chat UI sends
{"country", "city?"}from its browser memory with each/api/ask(or theasktool'slocationargument) — it wins overUSER_COUNTRY/set_location, but still loses to place names in the question. - Saved location breaks ties. A bare «قیمت بلیط اتوبوس» with
USER_COUNTRY=DEranks German options first; withTR, Turkish ones. - No cue, no location: both countries' options are returned ranked — your AI asks you which country you mean instead of guessing.
Every search result carries the server's country + one-line description, so the AI can itself disambiguate.
Privacy
Everything runs locally on your machine: stdio, no backend, no account, no telemetry. No API key is needed for search/call. Your location (env var, local file, or per-request hint) never leaves the machine. Child servers inherit your own session variables (see below) and nothing is ever logged, printed, or stored. The only network call the router itself makes is ask's routing call — and only when you configured a provider: your question goes to that provider (or stays on your machine with Ollama), and your key is sent only in the request header to that provider, never logged or stored.
Account actions (sessions)
Two servers have write tools that act inside your own account (cart, favorites): hepsiburada-mcp and migros-mcp. They use your own session cookie, passed as an env var in your MCP config — it never leaves your machine:
"env": {
"USER_COUNTRY": "DE",
"HEPSIBURADA_SESSION": "your-session-cookie",
"MIGROS_SESSION": "your-session-cookie"
}
Write actions always need explicit confirm=true in the arguments — enforced by the child servers, forwarded unchanged by the router. Payment is never automated: order tools return a checkout link and stop.
Servers not on PyPI yet (6)
These servers are in the index but their packages are not published yet, so call_tool returns a clear error instead of hanging: paribu-mcp, diyanet-mcp, osym-mcp, heise-mcp, zeit-mcp, welt-mcp. They will work automatically once published (the index regenerates on every factory run).
The hierarchy
- all-mcp (this repo) — the main reference: one entry point for everything.
- Turkey MCP + Germany MCP — the catalogs and platforms (turkey-mcp, germany-mcp).
- Individual MCP repos — one repo per service.
Every new server added by the daily factory runs updates this index too. The index is generated, never hand-written:
python3 gen_index.py # regenerate from the local catalogs
python3 gen_index.py --probe # also refresh real inputSchemas via uvx
gen_index.py is cron-friendly: non-interactive, idempotent (exit 0, file untouched when nothing changed), atomic writes, and a short summary on stdout. Factory cron command:
python3 ~/workspace/github-profile/projects/all-mcp/gen_index.py
Development
python -m pytest tests/ -q # offline suite (103 tests)
python tests/smoke_live.py # live smoke: 6 checks (needs network + uvx)
License
PolyForm Noncommercial 1.0.0 — free for personal and non-commercial use. Commercial use needs a separate license: contact Mohammad Abbasi.
Built by Mohammad Abbasi — https://almanibama.ir · https://mabbasi.ir
Metadata
Release files for all-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| all_mcp-0.1.0.tar.gz | 106.6 kB | With provenance | Details for all_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| all_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for all_mcp-0.1.0-py3-none-any.whl |
Total release size: 189.0 kB
Release files / all_mcp-0.1.0.tar.gz
| Download URL | all_mcp-0.1.0.tar.gz |
|---|---|
| Size | 106.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ff6195b95ed7ce07bd63f1aaf953bee8e18f32048d7de773438a9f825f30f0f
|
|
BLAKE2b-256 checksum How to use checksums |
2d4e8bc6350179e45ddae55f9c490bcd1ea42adf76a155e31addd18f03595132
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / all_mcp-0.1.0-py3-none-any.whl
| Download URL | all_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 82.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13c8d9635075a143a01c8e72b0c38c9a41336b7418786c6d36b6aae14336c3a4
|
|
BLAKE2b-256 checksum How to use checksums |
5d57d28d3028e5268c00bd4b562473a34d258dfab525e716d876c87e1e8a19a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for all-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for all_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.