Summary
The shortest path from a free TiDB cluster to an assistant that can see it.
There is no package to install and no account beyond TiDB Cloud: clone, create the venv, paste five environment variables. The README's Windows guidance is worth reading if you run under WSL, where the client has to invoke wsl.exe rather than uv directly.
What it is
A small MCP server for TiDB Serverless. It connects to a single cluster chosen at launch, so the assistant works against one database rather than being handed a connection string per request.
What you get
- A connection to one TiDB Serverless cluster, addressed by host and port — for example gateway01.us-east-1.prod.aws.tidbcloud.com on port 4000
- The database is pinned by TIDB_DATABASE, which defaults to test, so a session cannot wander into a neighbouring schema
- Configuration comes from environment variables or a .env file, which keeps the credentials out of the client config if you prefer
Requirements
A checkout of the repository and uv — installed with `uv venv` and `uv pip install -e .`, then launched as `uv --directory /path/to/mcp-server-tidb run src/main.py`. It needs TIDB_HOST, TIDB_PORT, TIDB_USERNAME, TIDB_PASSWORD and TIDB_DATABASE; a free cluster can be created at tidbcloud.com.