Control Plane OpenAPI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache time-to-live in seconds | 3600 |
| FACETS_TOKEN | No | Your Facets access token for API authentication | |
| FACETS_PROFILE | No | Facets profile to use from credentials file | default |
| FACETS_USERNAME | No | Your Facets username for API authentication | |
| CONTROL_PLANE_URL | No | Base URL of the Facets Control Plane | demo instance |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| FIRST_STEP_get_api_script_guideA | ALWAYS Call this tool first before calling any other tool of this mcp. Loads the API script generation guide that contains comprehensive instructions for creating scripts that interact with Control Plane APIs. Returns: str: A JSON string containing the content of the API script guide. |
| refresh_api_catalogA | Make Sure you have Called FIRST_STEP_get_api_script_guide first before this tool. Refresh the API catalog by fetching the latest OpenAPI specification. Returns: str: Success message confirming the catalog has been refreshed. |
| search_api_operationsA | Make Sure you have Called FIRST_STEP_get_api_script_guide first before this tool. Search for operations across the OpenAPI specification using fuzzy matching. Note: Only searches through active (non-deprecated) operations. Args: query (str): Search query to match against operation summaries, descriptions, tags, and operation IDs. Returns: str: JSON string containing matching operations with their details. |
| search_api_schemasA | Make Sure you have Called FIRST_STEP_get_api_script_guide first before this tool. Search for schemas across the OpenAPI specification using fuzzy matching. Args: query (str): Search query to match against schema names and descriptions. Returns: str: JSON string containing matching schemas with their details. |
| load_api_operation_by_operationIdA | Make Sure you have Called FIRST_STEP_get_api_script_guide first before this tool. Load a specific operation by its operationId. Args: operation_id (str): The unique operation ID to load. Returns: str: JSON string containing the complete operation details or null if not found. |
| load_api_operation_by_path_and_methodA | Make Sure you have Called FIRST_STEP_get_api_script_guide first before this tool. Load a specific operation by its path and HTTP method. Args: path (str): The API endpoint path (e.g., '/cc-ui/v1/stacks/{stackName}'). method (str): The HTTP method (GET, POST, PUT, DELETE, etc.). Returns: str: JSON string containing the complete operation details or null if not found. |
| load_api_schema_by_schemaNameA | Make Sure you have Called FIRST_STEP_get_api_script_guide first before this tool. Load a specific schema by its name. Args: schema_name (str): The name of the schema to load (e.g., 'Stack', 'ErrorDetails'). Returns: str: JSON string containing the complete schema details or null if not found. |
| call_control_plane_apiA | Make Sure you have Called FIRST_STEP_get_api_script_guide first before this tool. Make a GET request to the Facets Control Plane API. Args: path (str): API path to call (e.g., '/cc-ui/v1/stacks/my-stack' or 'cc-ui/v1/stacks') Returns: str: JSON string containing the API response or error information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| Control Plane API Script Generation | Prompt to be used for creating scripts that interact with Control Plane APIs. This will read from the `api_script_guide.md` file. Returns: The content of the prompt read from the markdown file. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Control Plane API Knowledge Base |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: getting the guide, refreshing the catalog, searching operations/schemas, loading specific operations/schemas, and calling the API. There is no overlap or ambiguity between them.
Naming is inconsistent: 'FIRST_STEP_get_api_script_guide' uses an odd prefix, 'load_api_operation_by_operationId' mixes snake_case with camelCase, and verbs vary (get, refresh, search, load, call). No consistent pattern across the set.
8 tools is well within the ideal range for an API discovery and invocation server. Each tool serves a necessary function without bloat or trivial additions.
The server covers the core workflow: loading the guide, refreshing the catalog, searching and loading operations/schemas, and making GET requests. However, it only supports GET calls and lacks a tool to list all operations/schemas in bulk, which are minor gaps.