Model Context Protocol server for CUBRID database
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cubrid-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<!-- CUBRID-LAB-ICON:START --> <p align="center"> <a href="https://github.com/cubrid-lab/brand"><img src="https://raw.githubusercontent.com/cubrid-lab/brand/e55990a6a0b2c3b0d133985951d41e42b62a8588/dist/icons/cubrid-mcp-server.svg" alt="cubrid-mcp-server icon (CUBRID Lab brand repository)" width="120"></a> </p> <!-- CUBRID-LAB-ICON:END --> # cubrid-mcp-server [](https://pypi.org/project/cubrid-mcp-server/) [](https://codecov.io/gh/cubrid-lab/cubrid-mcp-server) A [Model Context Protocol](https://modelcontextprotocol.io) server for [CUBRID](https://www.cubrid.org/), enabling LLMs to safely inspect schemas and execute read-only queries via [pycubrid](https://pypi.org/project/pycubrid/). <!-- mcp-name: io.github.cubrid-lab/cubrid-mcp-server --> <img src="docs/demo.gif" alt="Terminal recording: an MCP client lists the tools, calls all_table_names, and execute_query rejects DROP TABLE" width="100%"/> <sub>Terminal recording of a real MCP stdio session (<code>demos/mcp_demo.py</code>, recorded with <code>demos/record_demo.sh</code>).</sub> ## Start here New to CUBRID or to MCP? Follow the [Quick Start guide](docs/quickstart.md). It starts a disposable local CUBRID lab, prepares a sample table and a dedicated read-only account, connects one MCP client (a short Python script) and runs a first query, showing what each result means and how to clean up. The sections below are the reference for configuration, tools and client setup. ## Features | Tool | Description | |------|-------------| | `all_table_names` | List every user table in the database | | `filter_table_names` | Substring search over table names | | `schema_definitions` | Column types, nullability, defaults, and primary key info | | `describe_table` | Full metadata: columns, primary key, and indexes in one call | | `list_indexes` | Indexes for a table wit…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.