<b>A Model Context Protocol (MCP) server that enables natural language queries to databases</b>
A Model Context Protocol (MCP) server that enables natural language queries to databases. The xiyan mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Architecture — There are two ways to integrate this server in your project, as shown below: The left is remote mode, which is the default mode. It requires an APISTDIO — For stdio protocol, you can set just like this: yaml mcp: transport: "stdio"MySQL — The MySQL tool exposed by this serverPostgreSQL — Step 1: Install Python packages bash pip install psycopg2 Step 2: prepare the config.yml like this: yaml database: dialect: "postgresql" hostCline — The Cline tool exposed by this serverGoose — If you use stdio, add following command in the config, ref Goose config example shell env YML=path/to/yml /xxx/python -m xiyan_mcp_server OtherwiseCursor — The Cursor tool exposed by this serverWitsy — Add following in command: shell /xxx/python -m xiyan_mcp_server Add an env: key is YML and value is the path to your yml file. Ref Witsy configThe server ships on PyPI as xiyan-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Xiyan's toolset — Architecture, STDIO, MySQL and 5 more — is a fair guide to whether it matches your workflow. It is maintained by XGenerationLab; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Xiyan's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Architecture | There are two ways to integrate this server in your project, as shown below: The left is remote mode, which is the default mode. It requires an API key to access the xiyanSQL-qwencoder-32B model from service provider (se |
| STDIO | For stdio protocol, you can set just like this: yaml mcp: transport: "stdio" |
| MySQL | The MySQL tool exposed by this server. |
| PostgreSQL | Step 1: Install Python packages bash pip install psycopg2 Step 2: prepare the config.yml like this: yaml database: dialect: "postgresql" host: "localhost" port: 5432 user: "" password: "" database: "" |
| Cline | The Cline tool exposed by this server. |
| Goose | If you use stdio, add following command in the config, ref Goose config example shell env YML=path/to/yml /xxx/python -m xiyan_mcp_server Otherwise, if you use sse, change Type to SSE and set the endpoint to http://127.0 |
| Cursor | The Cursor tool exposed by this server. |
| Witsy | Add following in command: shell /xxx/python -m xiyan_mcp_server Add an env: key is YML and value is the path to your yml file. Ref Witsy config example |
For `sse`:
```json
{
"mcpServers": {
"xiyan_mcp_server_1": {
"url": "http://localhost:8000/sse"
}
}
}Configuration as documented by the project. Restart the client after saving.
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.