It allows you to - List tables, segments, and schema info from Pinot - Execute read-only SQL queries - View index/column-level metadata - Designed to
Connect MCP Pinot to Claude, Cursor or any other MCP client and it stops being a tab you switch to. It allows you to - List tables, segments, and schema info from Pinot - Execute read-only SQL queries - View index/column-level metadata - Designed to assist business users via Claude integration - and much more. The mcp pinot mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverAuthentication — An auth provider is required before binding HTTP or HTTPS to a non-loopback hostSetup — Copy the example configuration file: bash cp table_filters.yaml.example table_filters.yamlBuild — The Build tool exposed by this serverTest — Test the repo with: bash uv run pytest --cov=mcp_pinotBecause 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.
Configuration is passed through the environment: PINOT_CONTROLLER_URL, PINOT_BROKER_URL, PINOT_BROKER_HOST, PINOT_TOKEN, MCP_STATIC_TOKEN, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, OAUTH_BASE_URL. 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.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Pinot's toolset — Prerequisites, Installation, Authentication and 3 more — is a fair guide to whether it matches your workflow. It is maintained by startreedata; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Pinot's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Authentication | An auth provider is required before binding HTTP or HTTPS to a non-loopback host. |
| Setup | Copy the example configuration file: bash cp table_filters.yaml.example table_filters.yaml |
| Build | The Build tool exposed by this server. |
| Test | Test the repo with: bash uv run pytest --cov=mcp_pinot |
### Add an MCP server entry
```json
{
"mcpServers": {
"pinot_mcp": {
"command": "/path/to/uv",
"args": [
"--directory",
"/path/to/mcp-pinot-repo",
"run",
"mcp_pinot/server.py"
],
"env": {
// You can also include your .env config here
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PINOT_CONTROLLER_URL | Endpoint or connection string the server talks to. | Yes |
| PINOT_BROKER_URL | Endpoint or connection string the server talks to. | Yes |
| PINOT_BROKER_HOST | Endpoint or connection string the server talks to. | Optional |
| PINOT_TOKEN | Credential the server authenticates with. | Yes |
| MCP_STATIC_TOKEN | Credential the server authenticates with. | Yes |
| OAUTH_CLIENT_ID | Configuration value read at startup. | Optional |
| OAUTH_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| OAUTH_BASE_URL | Endpoint or connection string the server talks to. | Yes |
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.