cockpit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COCKPIT_URL | Yes | The URL of the Cockpit CMS instance (e.g., http://localhost:8080) | |
| COCKPIT_TOKEN | Yes | The API token for Cockpit CMS (created in Settings > API) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsA | List all Cockpit content models (collections & singletons) with a one-line summary each. Start here to see what content exists. |
| describe_modelA | Describe one content model's field schema (names, types, required, choices, linked models, nested fields). Use this to understand the exact shape of the data behind a page or component — instead of fetching the whole API or docs. |
| list_itemsA | List content items for a model. Supports an optional Mongo-style filter (JSON), sort, field projection, and limit. Read-only. |
| get_itemA | Get a single content item by its id. Read-only. |
| searchA | Find items in a model whose given text field matches a query (case-insensitive substring). Handy when you know the content but not the id. |
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 5 tools
Each tool targets a distinct operation: schema description, item retrieval by ID, filtered listing, model listing, and text search. No overlap in functionality.
Most tools use a clear verb_noun pattern (describe_model, get_item, list_items, list_models). 'search' deviates by omitting the noun but still follows the verb-first convention. Overall consistent.
Five tools is appropriate for a read-only content management server. Each tool serves a clear purpose without excess or deficiency.
The toolset fully covers the read-only domain: discover models, inspect schemas, retrieve items, and search. No gaps for the intended functionality.