Unified polyglot MCP server ecosystem
This repository aggregates all polyglot MCP (Model Context Protocol) servers from the hyperpolymath ecosystem. Each MCP provides unified access to multiple tools/services in its domain.
| MCP Server | Local-Agent | Hosted-HTTP | Security Boundary | CLI Wrapping |
|---|---|---|---|---|
✓ Yes |
✓ Yes |
Database credentials |
✗ No (direct drivers) |
|
✓ Yes |
✗ No |
kubeconfig / kubectl auth |
✓ Yes (kubectl, helm, kustomize) |
|
✓ Yes |
✗ No |
Cloud CLI credentials |
✓ Yes (aws, gcloud, az, doctl) |
|
✓ Yes |
✗ No |
Git forge tokens |
✓ Yes (gh, glab, tea) |
|
✓ Yes |
Partial |
Filesystem access |
✓ Yes (various SSG CLIs) |
|
✓ Yes |
✗ No |
Container runtime socket |
✓ Yes (nerdctl, podman, docker) |
-
Local-Agent (stdio): Runs as a subprocess of the MCP client. Has access to local filesystem, credentials, and can execute CLI tools.
-
Hosted-HTTP: Runs as a remote HTTP service. Cannot access local resources or execute CLI tools. Only poly-db-mcp fully supports this mode.
MCPs that wrap CLI tools use Deno’s --allow-run permission and inherit your local tool configurations:
|
Warning
|
CLI-wrapping MCPs (poly-k8s, poly-cloud, poly-git, poly-container) execute commands with your local credentials. The MCP client can perform any action you can perform with those tools. |
Recommendations:
-
Use minimal-permission credentials
-
Consider separate config profiles for MCP access
-
Review tool calls before approving in your MCP client
-
poly-db-mcp is safer for remote deployment (no CLI execution)
| Server | Description | Integrations |
|---|---|---|
poly-db-mcp |
20 databases through one interface |
PostgreSQL, MongoDB, Neo4j, Elasticsearch, Redis, SurrealDB, ArangoDB, CouchDB, Cassandra, SQLite, DuckDB, Qdrant, Meilisearch, MariaDB, Memcached, LMDB, InfluxDB, Virtuoso, iTop, XTDB |
| Server | Description | Integrations |
|---|---|---|
poly-k8s-mcp |
Kubernetes cluster management |
kubectl, Helm, Kustomize |
poly-cloud-mcp |
Multi-cloud provider management |
AWS, Google Cloud, Azure, DigitalOcean |
poly-container-mcp |
Container runtime operations |
nerdctl, podman, docker |
poly-mcps (central hub)
├── poly-db-mcp # Database connections (ReScript + Deno)
├── poly-k8s-mcp # Kubernetes (ReScript + Deno)
├── poly-cloud-mcp # Cloud providers (ReScript + Deno)
├── poly-git-mcp # Git forges (ReScript + Deno)
├── poly-ssg-mcp # Static site generators
└── poly-container-mcp # Container runtimes-
Core Language: ReScript (compiles to JavaScript)
-
Runtime: Deno (permissions model, TypeScript-free)
-
Protocol: MCP (Model Context Protocol)
-
Hosting: Local (stdio) or Deno Deploy (HTTP)
Each MCP server is its own repository. Clone the one you need:
# Databases (20 databases)
git clone https://github.com/hyperpolymath/poly-db-mcp
# Kubernetes
git clone https://github.com/hyperpolymath/poly-k8s-mcp
# Cloud providers
git clone https://github.com/hyperpolymath/poly-cloud-mcp
# Git forges
git clone https://github.com/hyperpolymath/poly-git-mcpSee each repository’s README for installation and configuration.