Cyoda Calculation Node MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CYODA_HOST | Yes | Your Cyoda host (e.g., client-<id>.eu.cyoda.net) | |
| CYODA_CLIENT_ID | Yes | Your Cyoda client ID | |
| CYODA_CLIENT_SECRET | Yes | Your Cyoda client secret |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| entity_get_entity_toolA | Retrieve a single entity by its technical ID. |
| entity_list_entities_toolB | List all entities of a specific type. |
| entity_create_entity_toolC | Create a new entity of a given model. |
| entity_update_entity_toolB | Update an existing entity. |
| entity_delete_entity_toolC | Delete an entity by ID. |
| search_find_allC | Find all entities of a specific type using entity_service.find_all(). |
| search_searchB | Search entities with Cyoda-native search conditions. |
| edge_message_get_edge_message_toolA | Retrieve an edge message by ID. |
| edge_message_send_edge_message_toolB | Send a new edge message. |
| workflow_mgmt_export_workflows_to_file_toolC | Export entity workflows to a JSON file. |
| workflow_mgmt_import_workflows_from_file_toolB | Import entity workflows from a JSON file. |
| workflow_mgmt_list_workflow_files_toolA | List available workflow files in the specified directory. |
| workflow_mgmt_validate_workflow_file_toolB | Validate a workflow file for correct JSON structure and required fields. |
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 13 tools
Most tools are clearly distinct by functional domain (edge messages, entities, workflows). The potential confusion between 'search_find_all' and 'search_search' is mitigated by their descriptions indicating different query capabilities, but an agent might still misselect.
Tool names follow inconsistent conventions: some use prefixes like 'edge_message_', 'entity_', 'workflow_mgmt_', while others use 'search_'. The naming mixes full words with abbreviations ('mgmt') and appends '_tool' inconsistently.
13 tools is a reasonable count for a server covering edge messages, entity CRUD, and workflow management. It is slightly on the higher side but not excessive.
The entity management covers CRUD and two search options, which is good. Edge messages lack delete/update. Workflow management is file-based and lacks direct lifecycle operations like create or delete, leaving notable gaps.