ClickHouse MCP Server for read-only database operations
Connect Clickhouse to Claude, Cursor or any other MCP client and it stops being a tab you switch to. ClickHouse MCP Server for read-only database operations. The clickhouse mcp server is what makes that connection.
A collection of Model Context Protocol (MCP) servers developed by Arvore for seamless integration with AI assistants like Claude.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Read — only operations for safetyMulti — environment support (production, test, etc.)Built — in SMTP server to receive real emailsDomain — wide delegation for full user-level accessSend — mode opt-in via GMAIL_MCP_ALLOW_SEND to prevent accidental sendsCategories — decisions, conventions, incidents, domain, gotchasWebSocket — based communication between agent and extensionReal — time console capture with start/stop controlCursor — based pagination with TTLInter — agent messaging (direct, broadcast, or to lead)WhatsApp — style message view with date separators and sender groupingAuto — refresh via filesystem watching (chokidar)Configuration is passed through the environment: DATADOG_API_KEY, DATADOG_APP_KEY, DATADOG_SITE, MYSQL_HOST, MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE, MYSQL_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.
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. Clickhouse's toolset — Read, Multi, Built and 11 more — is a fair guide to whether it matches your workflow. It is maintained by joao.barros.arvore; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Read | only operations for safety |
| Multi | environment support (production, test, etc.) |
| Built | in SMTP server to receive real emails |
| Domain | wide delegation for full user-level access |
| Send | mode opt-in via GMAIL_MCP_ALLOW_SEND to prevent accidental sends |
| Categories | decisions, conventions, incidents, domain, gotchas |
| WebSocket | based communication between agent and extension |
| Real | time console capture with start/stop control |
| Cursor | based pagination with TTL |
| Inter | agent messaging (direct, broadcast, or to lead) |
| style message view with date separators and sender grouping | |
| Auto | refresh via filesystem watching (chokidar) |
| Multi-session | claim/release cards with session tracking across parallel chats |
| Networking | VPCs, subnets, public IPs |
{
"mcpServers": {
"clickhouse-1": {
"command": "npx",
"args": ["-y", "@arvoretech/aws-secrets-manager-mcp"],
"env": {
"DATADOG_API_KEY": "your-value",
"DATADOG_APP_KEY": "your-value",
"DATADOG_SITE": "your-value",
"MYSQL_HOST": "your-value",
"MYSQL_USER": "your-value",
"MYSQL_PASSWORD": "your-value",
"MYSQL_DATABASE": "your-value",
"MYSQL_PORT": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DATADOG_API_KEY | Credential the server authenticates with. | Yes |
| DATADOG_APP_KEY | Credential the server authenticates with. | Yes |
| DATADOG_SITE | Configuration value read at startup. | Optional |
| MYSQL_HOST | Endpoint or connection string the server talks to. | Optional |
| MYSQL_USER | Configuration value read at startup. | Optional |
| MYSQL_PASSWORD | Configuration value read at startup. | Optional |
| MYSQL_DATABASE | Configuration value read at startup. | Optional |
| MYSQL_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.