openGauss MCP server build with FastMCP
LocalAbout openGauss MCP server build with FastMCP
This openGauss MCP server is built with FastMCP 2.0 and is intended for clients that need to connect an MCP workflow to an openGauss database. It supports three transport modes and configurable connection and server settings.
Key features
- 01Stdio, SSE, and Streamable-HTTP transports
- 02Configurable host, port, and path
- 03Database settings via environment or .env
Use cases
- 01Connecting an MCP client to openGauss
- 02Choosing a transport mode for deployment
MCP support
The MCP server connects to openGauss; the README does not specify which database operations or tools it exposes to clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEModel Context Protocol Server for openGauss
Features
- Build with FastMCP 2.0 .
- Support Stdio, SSE and Streamable-Http transporting method.
- MCP server transporting method, listerning port, host and path are Configurable via command-line argument.
- openGauss connection parameters are configurable via environment variables or .env files.
Deployment
Note: uv and python >= 3.12 is required.
git clone https://github.com/HowardQin/fastmcp-opengauss.git
cd fastmcp-opengauss
cp .env.example .env
uv sync
openGauss connection parameters are loaded from .env, for example:
OPENGAUSS_HOST=172.32.148.228
OPENGAUSS_PORT=31001
OPENGAUSS_USER=app
OPENGAUSS_PASSWORD=Postgres1234
OPENGAUSS_DBNAME=app
These parameters can be overwriten if identical environment variables are set.
Usage with Claude Desktop
Claude Desktop only supports Stdio mode, so we add the Stdio starting command in claude_desktop_config.json:
{
"mcpServers": {
"openGauss": {
"command": "uv",
"args": [
"--directory",
"C:\\Users\\qinh\\fastmcp-opengauss",
"run",
"server.py",
"--transport",
"stdio"
]
}
}
}
Usage with CherryStudio
CherryStudio supports all three transporting modes: Stdio, SSE and Streamable-Http
Stdio:
Arguments:
--directory
C:\Users\qinh\fastmcp-opengauss
run
server.py
--transport=stdio
SSE:
For SSE transport mode, we need to start a standalone mcp server, run following command in project root directory, or in any directory with --directory specifing project root dir :
uv --directory C:\Users\qinh\fastmcp-opengauss run .\server.py --transport=sse --port=8000 --path=/sse --host=0.0.0.0
Then configure CherryStudio to connect to sse mcp server:

Streamable-Http:
For Streamable-Http, we need to start a standalone mcp server, run following command in project root directory, or in any directory with --directory specifing project root dir:
uv --directory C:\Users\qinh\fastmcp-opengauss run .\server.py --transport=streamable-http --port=8000 --path=/mcp --host=0.0.0.0
Then configure CherryStudio to connect to streamable-http mcp server:

Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.