Provides AI assistants with a secure and structured way to explore and analyze data in GreptimeDB.
GreptimeDB becomes available to MCP clients through the greptimedb mcp server. Provides AI assistants with a secure and structured way to explore and analyze data in GreptimeDB.
A Model Context Protocol (MCP) server for GreptimeDB — an open-source observability database that handles metrics, logs, and traces in one engine.
Once connected, the assistant can call these 7 tools directly:
execute_sql — Execute SQL queries with format (csv/json/markdown) and limit optionsexecute_tql — Execute TQL (PromQL-compatible) queries for time-series analysisquery_range — Execute time-window aggregation queries with RANGE/ALIGN syntaxdescribe_table — Inspect a table profile: schema, semantic metadata, latest sample rows, and query guidanceexplain_query — Analyze SQL or TQL query execution plans (analyze=true for runtime stats; add verbose=true alongside analyze=true for per-partition scan metrics andhealth_check — Check database connection status and server versionTools — The Tools tool exposed by this serverThe server is distributed via npm as @modelcontextprotocol/inspector, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
The server reads 2 environment variables: GREPTIMEDB_HOST, GREPTIMEDB_LISTEN_HOST. Keep credentials in your client's env block or a secrets manager rather than committing them.
Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. GreptimeDB sits in that group, and the shape of its toolset — execute_sql, execute_tql, query_range among others — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| execute_sql | Execute SQL queries with format (csv/json/markdown) and limit options |
| execute_tql | Execute TQL (PromQL-compatible) queries for time-series analysis |
| query_range | Execute time-window aggregation queries with RANGE/ALIGN syntax |
| describe_table | Inspect a table profile: schema, semantic metadata, latest sample rows, and query guidance |
| explain_query | Analyze SQL or TQL query execution plans (analyze=true for runtime stats; add verbose=true alongside analyze=true for per-partition scan metrics and index-pruning counters) |
| health_check | Check database connection status and server version |
| Tools | The Tools tool exposed by this server. |
{
"mcpServers": {
"greptimedb": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"GREPTIMEDB_HOST": "your-value",
"GREPTIMEDB_LISTEN_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GREPTIMEDB_HOST | Endpoint or connection string the server talks to. | Optional |
| GREPTIMEDB_LISTEN_HOST | Endpoint or connection string the server talks to. | 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.