Which one you install follows from what you operate: obdiag for reading logs and running inspections when something is wrong, okctl if the clusters live in Kubernetes, obshell for deployment, and the database server itself for plain SQL. They are separate installs, and the diagnostic ones expect their underlying command-line tool to be present and already configured.
The OceanBase team's repository of MCP servers for their own ecosystem. Rather than one server it publishes eight: the database itself, the OCP cloud platform, OBCloud, `okctl` for Kubernetes, the `obdiag` diagnostic tool, `obshell` for cluster operations, seekdb for vector work, and PowerMem for AI memory.
- OceanBase MCP Server — SQL queries and data management against an OceanBase instance
- Obdiag MCP Server for diagnosis: `obdiag_check_run` returns an inspection report, `obdiag_analyze_log` finds errors that already occurred, `obdiag_gather_log` collects logs filtered by time range or grep, and `obdiag_cluster_list` names the clusters it can address
- Okctl MCP Server for OceanBase on Kubernetes — `list_all_clusters`, `show_cluster`, `scale_cluster`, `upgrade_cluster`, tenant work including `switchover_tenant` and `activate_tenant`, backup policies, and `execute_cluster_sql` for queries
- Obshell MCP Server for cluster creation, deployment and operations management
- OCP MCP Server for cluster management and monitoring, and OBCloud MCP Server for the cloud service
- Seekdb MCP Server — vector operations, collection management, SQL and AI functions for the seekdb database
- PowerMem MCP Server for memory storage, search and retrieval with an Ebbinghaus forgetting curve
An OceanBase instance to point at; there is a free trial if you do not have one. Each server installs separately, with its own prerequisites. `uvx obdiag-mcp` takes a mode — `stdio`, `sse` or `streamable-http`, sse on port 8000 by default — and needs obdiag itself installed with at least one config file in `~/.obdiag/`, one `.yml` per cluster. `uvx obshell-mcp` reads `OBSHELL_HOST`, `OBSHELL_PORT`, `CLUSTER_NAME` and `SYS_PASSWORD`. The okctl server needs Python 3.10 or higher, the okctl CLI installed, a Kubernetes context with access to your clusters, and `OB_CLUSTER_PASSWORD` for the sys tenant; `--tools` narrows what it exposes to any of clusters, tenants, backup_policy, components and sql.
One command plus a key — uvx obshell-mcp, then supply credentials