Cyoda Calculation Node MCP
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Cyoda Calculation Node MCP create a new entity of type Contact with name 'John Doe'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cyoda Calculation Node Application
A comprehensive application framework for building calculation nodes within the Cyoda platform. This project provides a structured foundation for developing entity-driven applications with workflow automation, built on the asynchronous Quart web framework.
What is This?
This is a Cyoda Calculation Node - a specialized application that:
Manages entities (structured data models) within the Cyoda ecosystem
Executes workflows (finite-state machines) to process entity state transitions
Integrates with the Cyoda platform via gRPC for seamless data synchronization
Provides REST APIs for entity management and workflow operations
Supports AI assistant integration through the Model Context Protocol (MCP)
Related MCP server: Relatio CRM MCP Server
Project Structure
├── application/ # Your application code (entities, workflows, routes)
├── common/ # Shared infrastructure (auth, config, gRPC, repository)
├── cyoda_mcp/ # MCP server for AI assistant integration
├── example_application/ # Reference implementation
├── services/ # Service configuration and initialization
└── tests/ # Comprehensive test suiteKey Directories
application/- Your custom business logicentity/- Entity definitions and workflow implementationsroutes/- REST API endpointsprocessor/- Custom processors and criteria functions
cyoda_mcp/- MCP server for AI integrationSee cyoda_mcp/README.md for MCP server documentation
common/- Shared infrastructure (do not modify unless necessary)auth/- Authentication and token managementconfig/- Configuration and environment variablesgrpc_client/- Cyoda gRPC integrationrepository/- Data access layerservice/- Business logic interfaces
example_application/- Reference implementation showing best practices
Quick Start
1. Set Up Environment
# Clone the repository
git clone <repository-url>
cd mcp-cyoda-quart-app
# Create virtual environment
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
# Install dependencies
pip install -r requirements.txt2. Configure Credentials
export CYODA_CLIENT_ID="your-client-id"
export CYODA_CLIENT_SECRET="your-client-secret"
export CYODA_HOST="client-<id>.eu.cyoda.net"3. Run the Application
# Run the application server
python -m application.app
# Or run the MCP server for AI integration
python -m cyoda_mcpMCP Server Integration
This project includes a Model Context Protocol (MCP) server that enables AI assistants to interact with your Cyoda application.
For complete MCP server documentation, see: cyoda_mcp/README.md
Quick MCP Setup
# Install globally
pipx install mcp-cyoda
# Run the server
mcp-cyodaDevelopment
Code Quality
# Run all quality checks
python -m black . && python -m isort . && python -m mypy . && python -m flake8 . && python -m bandit -r .
# Run tests
python -m pytest tests/ -vContributing
See CONTRIBUTING.md for detailed contribution guidelines.
Documentation
CONTRIBUTING.md - Contribution guidelines and development workflow
AI_TESTING_GUIDE.md - Testing with AI assistants
CYODA_E2E_TESTING_GUIDE.md - End-to-end testing procedures
cyoda_mcp/README.md - MCP server documentation
docs/ - Architecture and design documentation
Getting Help
Cyoda Platform: https://ai.cyoda.net
Documentation: https://docs.cyoda.net
Issues: GitHub Issues
License
MIT License - See LICENSE for details
Available Tools
13 toolsedge_message_get_edge_message_toolA
Retrieve an edge message by ID.
Inputs: message_id (required). Returns: object
edge_message_send_edge_message_toolB
Send a new edge message.
Inputs: subject (required), content (required), message_id, user_id, +6 more. Returns: object
entity_create_entity_toolC
Create a new entity of a given model.
Inputs: entity_model (required), entity_data (required), entity_version. Returns: object
entity_delete_entity_toolC
Delete an entity by ID.
Inputs: entity_model (required), entity_id (required), entity_version. Returns: object
entity_get_entity_toolA
Retrieve a single entity by its technical ID.
Inputs: entity_model (required), entity_id (required), entity_version. Returns: object
entity_list_entities_toolB
List all entities of a specific type.
Inputs: entity_model (required), entity_version. Returns: object
entity_update_entity_toolB
Update an existing entity.
Inputs: entity_model (required), entity_id (required), entity_data (required), entity_version. Returns: object
search_find_allC
Find all entities of a specific type using entity_service.find_all().
Inputs: entity_model (required), entity_version. Returns: object
search_searchB
Search entities with Cyoda-native search conditions.
Inputs: entity_model (required), search_conditions (required), entity_version. Returns: object
workflow_mgmt_export_workflows_to_file_toolC
Export entity workflows to a JSON file.
Inputs: entity_name (required), model_version (required), file_path (required). Returns: object
workflow_mgmt_import_workflows_from_file_toolB
Import entity workflows from a JSON file.
Inputs: entity_name (required), model_version (required), file_path (required), import_mode. Returns: object
workflow_mgmt_list_workflow_files_toolA
List available workflow files in the specified directory.
Inputs: base_path. Returns: object
workflow_mgmt_validate_workflow_file_toolB
Validate a workflow file for correct JSON structure and required fields.
Inputs: file_path (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Official MCP bridge to Exogram—the Personal AI Agent for your work, people, and life.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI-powered document automation and data manipulation with Coda.io through the Model Context Protocol, supporting document, page, table, row, and formula operations.2659 PyPI6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage CRM prospects, activities, reminders, and mailbox via natural language commands through the Model Context Protocol.3MIT

@vitrion/zentria-mcpofficial
AlicenseBqualityBmaintenanceEnables AI assistants to access and manage Zentria CRM data, including sales, customers, to-dos, and more, through the Model Context Protocol.80595 npmMIT- FlicenseNot gradedqualityAmaintenanceEnables users to control supported CAD applications through AI assistants using the Model Context Protocol, supporting drawing, layers, entities, blocks, files, exports, and natural-language automation.-