cyberday-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CYBERDAY_API_KEY | Yes | Your Cyberday API key (requires admin access to generate) |
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 |
|---|---|
| list_systemsA | List data systems (tietojärjestelmät) registered in Cyberday. Returns a compact overview of each system with key fields: name, status, owner, hosting, business units, etc. Use 'get_system' with a specific ID to see full details of a single system. Supports pagination with 'limit' and 'offset' parameters. |
| search_systemsA | Search and filter data systems by name, description, status, hosting type, or assigned user. Returns compact results with key fields. Use 'get_system' for full details. All filters are combined with AND logic. Text searches are case-insensitive. Example statuses: 'Käsitelty' (done), 'Aktiivinen' (active), 'Ei käytössä' (not in use). |
| get_systemA | Get full details of a specific data system by its ID. Returns all available fields with human-readable names, including purpose, hosting, processors, access controls, integrations, etc. Empty fields are omitted from the response. Use 'list_systems' or 'search_systems' first to find system IDs. |
| create_systemA | Create a new data system in Cyberday with a given title. Returns the created system details. For adding extended details (owner, hosting, processors, etc.), use 'create_system_advanced'. |
| create_system_advancedB | Create or update a data system in Cyberday with extended details. If a system with the given title already exists, it will be updated with the provided fields. Fields not provided will remain unchanged for existing systems. |
| systems_summaryA | Get a high-level overview of all data systems in Cyberday. Returns: total count, status breakdown, systems overdue for review, framework coverage, and CIA importance distribution. This is the best starting point to understand the current state of your data systems. |
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 6 tools
Most tools are clearly distinct: list/search/get handle different retrieval needs, and systems_summary provides aggregate analytics. However, create_system and create_system_advanced overlap on creation, which could cause an agent to choose the wrong one when extended fields are needed.
Five tools follow a consistent verb_noun snake_case pattern (list_systems, search_systems, get_system, create_system, create_system_advanced). The outlier systems_summary uses a noun_noun style, but the overall convention remains readable and predictable.
With six tools, the set is well-scoped for a data-system registry MCP. Each tool covers a distinct operation or aggregation need, and the count avoids both excessive fragmentation and under-provisioning.
The surface covers list, search, get, create, update-via-advanced-create, and summary analytics. The main gap is a dedicated delete or archive operation, which is a minor omission for a registry but not a severe workflow blocker.