CnosDB MCP Server

What is CnosDB MCP Server?

CnosDB MCP Server is a Model Context Protocol (MCP) server that enables Claude Desktop and other MCP clients to interact with a CnosDB database. It allows users to list databases, list tables, describe table schemas, and execute arbitrary SQL queries against a CnosDB instance. Designed for developers and data analysts who manage time‑series data in CnosDB.

How to use CnosDB MCP Server?

Clone the repository, create a Python virtual environment, install dependencies, then configure Claude Desktop by adding a JSON entry in claude_desktop_config.json specifying the uv command, the server script path, and connection environment variables. The server exposes four tools: query, list_databases, list_tables, and describe_table.

Key features of CnosDB MCP Server

• Execute SQL queries against CnosDB
• List all databases in the CnosDB instance
• List tables within a specific database
• Display the schema of a given table
• Environment‑based configuration for host, port, username, and password

Use cases of CnosDB MCP Server

• Query time‑series data stored in CnosDB via natural language in Claude
• Inspect database structure and table schemas during development
• Automate database exploration and reporting without a separate client
• Integrate CnosDB data into AI‑assisted analysis workflows

FAQ from CnosDB MCP Server

What does CnosDB MCP Server do?

It connects MCP clients (like Claude Desktop) to a CnosDB database, enabling natural language or programmatic requests to list databases, tables, view schemas, and run SQL queries.

What dependencies are required to run CnosDB MCP Server?

Python 3.12 and the uv tool are required. Development dependencies are installed via pip install -r requirements.txt. No additional runtime dependencies beyond a running CnosDB instance.

How does CnosDB MCP Server authenticate to the database?

Authentication is configured via environment variables CNOSDB_USERNAME and CNOSDB_PASSWORD in the MCP client configuration file. Default credentials are root / CnosDB#!.

Where does the data live and how is it accessed?

The server connects to a CnosDB service specified by CNOSDB_HOST and CNOSDB_PORT (defaults 127.0.0.1:8902). All queries are executed against that remote database; the server does not store or cache data locally.

What transports does CnosDB MCP Server support?

The MCP server uses the standard stdio transport, invoked via uv from the Claude Desktop configuration. It does not support HTTP or WebSocket transports natively.