mcp-oceanbase
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| configure_db_connectionA | |
| execute_sqlC | Execute an SQL on the OceanBase server. |
| get_ob_ash_reportC | |
| get_current_timeC | Get current time |
| get_current_tenantB | Get the current tenant name from oceanbase. |
| get_all_server_nodesA | Get all server nodes from oceanbase. You need to be sys tenant to get all server nodes. |
| get_resource_capacityB | Get resource capacity from oceanbase. You need to be sys tenant to get resource capacity. |
| search_oceanbase_documentC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_tables | list all tables |
TDQS
Scored across 8 tools
Most tools have distinct purposes, such as configure_db_connection for setup, execute_sql for queries, and get_ob_ash_report for performance analysis. However, get_current_time and get_current_tenant could be confused as both retrieve basic system information, though their descriptions clarify the difference.
The tool names follow a consistent verb_noun pattern with underscores, like configure_db_connection and execute_sql. A minor deviation is search_oceanbase_document, which uses 'search' instead of 'get' like other retrieval tools, but overall the naming is predictable and readable.
With 8 tools, this server is well-scoped for OceanBase database management. The count is appropriate, covering configuration, query execution, monitoring, and documentation without being overwhelming or too sparse, allowing agents to handle core database tasks effectively.
The tool set covers key areas like connection setup, SQL execution, and monitoring (e.g., ASH reports, resource capacity), but there are notable gaps. Missing operations include data manipulation (e.g., insert, update, delete), schema management (e.g., create table), and user/tenant administration, which limits full database lifecycle coverage.