In-process MCP gateway that routes an LLM to database operations across many engines
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"polyglot-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# polyglot-mcp (Python) In-process MCP gateway that routes an LLM to database operations across many engines (PostgreSQL, MySQL, SQLite, MongoDB, Redis, S3/MinIO). It wraps the [`polyglot-core`](../polyglot-core) library and exposes each operation as an MCP tool. Connections are pre-registered in a JSON config referenced by `POLYGLOT_CONFIG`; the LLM only ever passes a connection *name*. ```bash POLYGLOT_CONFIG=connections.json python -m polyglot_mcp.server ``` ## Tools `list_connections`, `describe_connection`, `health_check`, `list_namespaces`, `list_tables`, `describe_table`, `run_query`, `explain_query`, `execute`, `sample_data`, `count_rows`, `copy_data`. ## Transports Defaults to **stdio** (Claude Desktop / Claude Code). For a remote/browser client, serve over HTTP: `polyglot-mcp --http` (or `POLYGLOT_TRANSPORT=http`), with `POLYGLOT_HOST` / `POLYGLOT_PORT` (default `127.0.0.1:8000`). See `../TESTING.md` for a natural-language test script you can run from a Claude client, and `../examples/` for a ready-to-use config and docker-compose stack.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.