This repository contains MCP (Model Context Protocol) servers and an ADK agent for database querying and Kubernetes cluster management:
Most database access work still happens through a UI a human drives. MCP Ran Poc MCP server moves it into the conversation instead. This repository contains MCP (Model Context Protocol) servers and an ADK agent for database querying and Kubernetes cluster management:.
The server publishes 1 tool. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverConfiguration is passed through the environment: KUBECONFIG, ALARMS_DB_HOST, ALARMS_DB_PORT, ALARMS_DB_NAME, ALARMS_DB_USER, ALARMS_DB_PASSWORD, RESOURCES_DB_HOST, RESOURCES_DB_PORT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
oc) installed and logged in - Docker/Podman for building images - Access to a container registry (quay.io)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Ran Poc's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by pixelsoccupied; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
#### PostgreSQL Server Configuration
```json
{
"mcpServers": {
"postgres": {
"command": "uv",
"args": [
"run",
"python", "servers/ocloud-pg.py"
],
"cwd": "/path/to/mcp-ran-poc",
"env": {
"ALARMS_DB_HOST": "your-postgres-host",
"ALARMS_DB_PORT": "5432",
"ALARMS_DB_NAME": "alarms",
"ALARMS_DB_USER": "alarms",
"ALARMS_DB_PASSWORD": "your-password",
"RESOURCES_DB_HOST": "your-postgres-host",
"RESOURCES_DB_PORT": "5432",
"RESOURCES_DB_NAME": "resources",
"RESOURCES_DB_USER": "resources",
"RESOURCES_DB_PASSWORD": "your-password",
"CLUSTERS_DB_HOST": "your-postgres-host",
"CLUSTERS_DB_PORT": "5432",
"CLUSTERS_DB_NAME": "clusters",
"CLUSTERS_DB_USER": "clusters",
"CLUSTERS_DB_PASSWORD": "your-password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
oc) installed and logged in - Docker/Podman for building images - Access to a container registry (quay.io)| Variable | Description | Required |
|---|---|---|
| KUBECONFIG | Configuration value read at startup. | Optional |
| ALARMS_DB_HOST | Endpoint or connection string the server talks to. | Optional |
| ALARMS_DB_PORT | Configuration value read at startup. | Optional |
| ALARMS_DB_NAME | Configuration value read at startup. | Optional |
| ALARMS_DB_USER | Configuration value read at startup. | Optional |
| ALARMS_DB_PASSWORD | Configuration value read at startup. | Optional |
| RESOURCES_DB_HOST | Endpoint or connection string the server talks to. | Optional |
| RESOURCES_DB_PORT | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.