Go [tidbcloud.com](https://tidbcloud.com) to create a free TiDB database cluster
Tidb MCP server exists for a simple reason — assistants are far more useful when they can act on Tidb directly instead of describing what you should do. Go tidbcloud.com to create a free TiDB database cluster.
Once Tidb is connected, these are the calls the assistant has available:
TIDB_HOST — TiDB host address, e.g. 'gateway01.us-east-1.prod.aws.tidbcloud.com'TIDB_PORT — TiDB port (default: 4000)TIDB_USERNAME — Database username, e.g. 'xxxxxxxxxx.<username>'TIDB_PASSWORD — Database passwordTIDB_DATABASE — Database name, default is testYou will need one environment variable: TIDB_HOST. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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. Tidb's toolset — TIDB_HOST, TIDB_PORT, TIDB_USERNAME and 2 more — is a fair guide to whether it matches your workflow. It is maintained by c4pt0r; 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 |
|---|---|
| TIDB_HOST | TiDB host address, e.g. 'gateway01.us-east-1.prod.aws.tidbcloud.com' |
| TIDB_PORT | TiDB port (default: 4000) |
| TIDB_USERNAME | Database username, e.g. 'xxxxxxxxxx.\<username\>' |
| TIDB_PASSWORD | Database password |
| TIDB_DATABASE | Database name, default is test |
{
"mcpServers": {
"tidb": {
"command": "uv",
"args": [
"--directory",
"/path/to/mcp-server-tidb",
"run",
"src/main.py"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TIDB_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.