@severalnines/ccx-admin-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CCX_PROTECT | No | Block destructive tools (default true). Set to false to unlock destructive tools. | true |
| CCX_BASE_URL | Yes | Base URL of the CCX deployment. Must be https:// (plain http:// is only accepted for localhost). | |
| CCX_ENV_FILE | No | Explicit .env location. If not given, server looks for .env next to package.json. | |
| CCX_ADMIN_PASSWORD | Yes | Admin user password. | |
| CCX_ADMIN_USERNAME | Yes | Admin user login email. | |
| CCX_ADMIN_BASIC_PASSWORD | No | HTTP basic auth password (optional). | |
| CCX_ADMIN_BASIC_USERNAME | No | HTTP basic auth user (optional). |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ccx_admin_checkA | Verify connectivity and credentials against the CCX admin API. Reports the admin REST health check (basic auth) and the admin session identity (admin user login), whichever credentials are configured. |
| ccx_admin_cmon_versionA | Get the version of the ClusterControl controller (cmon) backing this CCX deployment. |
| ccx_admin_count_datastoresA | Total number of datastores (database clusters) across all CCX users. Uses the basic-auth counter endpoint when basic credentials are configured, otherwise counts the full datastore list via the admin session. |
| ccx_admin_count_usersA | Count CCX users. The basic-auth counter endpoint (/admin/users/count) counts customer accounts: it excludes @severalnines.com / @s9s.io logins in production and still includes deleted users. When an admin session is configured the full user list is also counted client-side, broken down by internal/external, suspended and deleted, so the two numbers can be reconciled. |
| ccx_admin_list_vpcsA | List VPC ids known to CCX for an AWS region, with dangling-VPC detection fields. Requires basic auth credentials. NOTE: the backend currently only fills ccx_num_vpcs/ccx_vpc_ids and may return zero even when VPCs exist; treat an empty result as 'unknown', not 'none'. |
| ccx_admin_list_datastoresA | List datastores (database clusters) across ALL CCX users, with owner, status and the latest job. The API returns everything in one call; filters are applied client-side. Status values include STARTED, DEGRADED, FAILURE, STOPPED, UNKNOWN, and CCX lifecycle states such as creating_cluster, deploy_failed, deleting, unreachable. |
| ccx_admin_get_datastoreA | Get one datastore by UUID regardless of owner: status, owner login, cmon internal cluster id, the latest job (including its raw data) and the database nodes. |
| ccx_admin_list_nodesA | List the database and load-balancer nodes of a datastore: hostname, IP, role, cmon host status (e.g. CmonHostOnline), DB version, cloud instance id/type and availability zone. |
| ccx_admin_get_datastore_auditA | Query the audit log of a datastore (jobs, resource create/delete, info lines), newest first. Time bounds are RFC3339 timestamps, e.g. 2026-09-01T00:00:00Z. |
| ccx_admin_delete_datastoreA | FORCE-DELETE any user's datastore as admin. This destroys the cluster and its data and cannot be undone. Requires confirm=true and is blocked while protection mode (CCX_PROTECT) is on. |
| ccx_admin_list_usersA | List all CCX users with id, login, name, creation time and suspended/deleted flags. The API returns everything; filters are applied client-side. |
| ccx_admin_suspend_userA | Suspend a CCX user so they can no longer log in or use their datastores. Reversible with ccx_admin_unsuspend_user. Blocked while protection mode (CCX_PROTECT) is on. |
| ccx_admin_unsuspend_userA | Lift a suspension so the CCX user can log in and use their datastores again. |
| ccx_admin_delete_userA | Delete a CCX user account. This cannot be undone. Requires confirm=true and is blocked while protection mode (CCX_PROTECT) is on. Consider ccx_admin_suspend_user instead. |
| ccx_admin_billing_usageA | Per-datastore resource usage for a date range across all customers: instance hours by instance type, volume GiB-hours and IOPS, network egress and backup counts/sizes. Dates are YYYY-MM-DD and inclusive; 'to' defaults to today. Includes datastores deleted during the period. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action: health check, VPC listing, datastore listing/retrieval/deletion/audit, node listing, user management, and billing. Even the similar count/list pairs are clearly separated by endpoint semantics and client-side reconciliation.
All tools share the ccx_admin_ prefix and use snake_case, with most following a clear verb_noun pattern like list_datastores, get_datastore, and suspend_user. A few names like cmon_version and billing_usage omit an explicit verb, but they are still predictable and consistent in style.
Fifteen tools is at the upper edge of the ideal range, but every tool covers a distinct admin operation with no apparent redundancy. The scope is broad—VPCs, datastores, users, billing, health—so each tool earns its place.
The surface provides solid lifecycle coverage for the admin domain: health, listing, inspection, deletion, audit, user suspension, and billing. Minor gaps exist, such as no admin user creation or datastore modification, but these are not core admin destructive/read-only operations and can be worked around.