Signavio MCP Server
Provides comprehensive integration with SAP Signavio Process Manager API, enabling management of process models, folders, dictionary entries, glossary categories, and content search. Supports model operations including creation, updating, exporting (JSON, BPMN, PNG, SVG), and publishing to Collaboration Hub.
Signavio MCP Server
A comprehensive Model Context Protocol (MCP) server that provides seamless integration between SAP Signavio Process Manager and AI-powered development tools. This server exposes the complete Signavio API as a set of tools, enabling AI assistants like Claude, Cursor, and other MCP-compatible clients to interact with your Signavio workspace programmatically.
Overview
The Signavio MCP Server bridges the gap between business process management and AI-assisted development workflows. Whether you're automating process documentation, managing business process models, maintaining process dictionaries, or integrating Signavio data into your development pipeline, this server provides a unified interface for all Signavio API operations.
Key Features
Complete API Coverage: Full access to Signavio Process Manager API endpoints including models, folders, dictionary entries, and search functionality
AI Assistant Integration: Seamlessly works with Claude, Cursor, and other MCP-compatible AI development tools
Business Process Automation: Automate process model creation, updates, exports, and management tasks
Dictionary Management: Create, update, and search business process dictionaries and glossary entries
Multi-format Export: Export process models in JSON, BPMN 2.0 XML, PNG, and SVG formats
Search Capabilities: Full-text search across models, revisions, files, and dictionary entries
Zero Configuration: Run directly with npx or install locally for development
Related MCP server: bw-modeling-mcp
Prerequisites
Node.js (v14 or higher)
npm or yarn
Signavio account with API access
Your Signavio tenant ID (Workspace ID)
Installation
Option 1: Using npx (Recommended)
No installation required! You can run the MCP server directly using npx:
npx signavio-mcpOption 2: Local Installation
Install the package:
npm install signavio-mcpOr clone the repository:
git clone https://github.com/willpowell8/signavio-mcp.git cd signavio-mcp npm install
Configuration
Configure environment variables:
Create a .env file in the project root with your credentials:
SIGNAVIO_BASE_URL=https://api.eu.signavio.cloud.sap
SIGNAVIO_EMAIL=your-email@example.com
SIGNAVIO_PASSWORD=your-password
SIGNAVIO_TENANT=your-tenant-idNote: The base URL is region-specific. Use the appropriate URL for your region:
EU:
https://api.eu.signavio.cloud.sapUSA:
https://api.us.signavio.cloud.sapAustralia:
https://api.au.signavio.cloud.sapCanada:
https://api.ca.signavio.cloud.sapJapan:
https://api.jp.signavio.cloud.sapSingapore:
https://api.sgp.signavio.cloud.sapSouth Korea:
https://api.kr.signavio.cloud.sap
Finding Your Tenant ID
To find your tenant ID (Workspace ID):
Log in to SAP Signavio Process Manager
In the Explorer, go to Help menu
Select Workspace information
Copy the Workspace ID - this is your tenant ID
Security Notes
Never commit your
.envfile to version controlThe
.envfile should be included in.gitignoreConsider using environment variables or a secrets manager for production use
MCP Server Configuration
The MCP server uses environment variables from your .env file. You can also:
Set environment variables in your system
Pass environment variables when starting the server
MCP Client Configuration
For Cursor or other MCP-compatible clients, add this to your MCP configuration:
Using npx (Recommended):
{
"mcpServers": {
"signavio-api": {
"command": "npx",
"args": ["-y", "signavio-mcp"],
"env": {
"SIGNAVIO_BASE_URL": "https://api.eu.signavio.cloud.sap",
"SIGNAVIO_EMAIL": "your-email@example.com",
"SIGNAVIO_PASSWORD": "your-password",
"SIGNAVIO_TENANT": "your-tenant-id"
}
}
}
}Using locally installed package:
{
"mcpServers": {
"signavio-api": {
"command": "node",
"args": ["/path/to/node_modules/signavio-mcp/mcp-server.js"],
"env": {
"SIGNAVIO_BASE_URL": "https://api.eu.signavio.cloud.sap",
"SIGNAVIO_EMAIL": "your-email@example.com",
"SIGNAVIO_PASSWORD": "your-password",
"SIGNAVIO_TENANT": "your-tenant-id"
}
}
}
}Available MCP Tools
The MCP server provides the following tools:
Authentication
signavio_authenticate- Authenticate with Signavio API
Directory/Folder Operations
signavio_get_root_folders- Get workspace root folderssignavio_get_folder_contents- Get folder contents by IDsignavio_create_folder- Create a new foldersignavio_update_folder- Rename or update folder descriptionsignavio_move_folder- Move folder to new parent or trashsignavio_delete_folder- Permanently delete a folder
Dictionary/Glossary Operations
signavio_search_dictionary- Search dictionary entriessignavio_get_dictionary_entry- Get specific dictionary entrysignavio_create_dictionary_entry- Create new dictionary entrysignavio_update_dictionary_entry- Update dictionary entrysignavio_delete_dictionary_entry- Delete dictionary entrysignavio_get_dictionary_categories- Get all dictionary categoriessignavio_get_dictionary_category- Get specific categorysignavio_create_dictionary_category- Create new category
Model Operations
signavio_get_model- Get model metadatasignavio_get_model_revisions- Get all model revisionssignavio_export_model- Export model (json, bpmn2_0_xml, png, svg)signavio_create_model- Create new model/diagramsignavio_update_model- Update model (creates new revision)signavio_move_model- Move model to different foldersignavio_publish_model- Publish model(s) to Collaboration Hub
Search Operations
signavio_search- Full-text search across all content types
Running the MCP Server
Using npx (Recommended):
npx signavio-mcpUsing locally installed package:
npm startOr directly:
node mcp-server.jsTesting the MCP Server
A comprehensive test script is available to verify all MCP server functionality:
npm testOr directly:
node test-mcp-server.jsThe test script will:
✅ Test authentication
✅ Test directory/folder operations (get root folders, get folder contents)
✅ Test dictionary operations (categories, search, get entries)
✅ Test model operations (search, get model, get revisions, export)
✅ Test search functionality
✅ Provide a detailed summary of all tests
Note: The test script uses your .env configuration and will skip tests that require existing data (like getting a specific model) if no data is found. This is expected behavior for a clean workspace.
API Documentation
For more information about the Signavio API, refer to the SAP Signavio Process Manager API Guide.
Available Tools
23 toolsTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Every tool has a clearly distinct purpose targeting specific resources and actions. For example, signavio_create_dictionary_entry, signavio_get_dictionary_entry, signavio_update_dictionary_entry, and signavio_delete_dictionary_entry form a complete CRUD set for dictionary entries, with no overlap in functionality. Tools like signavio_export_model and signavio_publish_model serve unique export and publishing roles, making misselection unlikely.
All tools follow a consistent verb_noun pattern with the prefix 'signavio_' and snake_case throughout. The naming convention is predictable, using verbs like create, get, update, delete, move, export, publish, and search paired with specific nouns (e.g., dictionary_entry, folder, model). This uniformity enhances readability and usability for agents.
With 23 tools, the count is slightly high but reasonable for a comprehensive BPM/process modeling server like Signavio. It covers multiple domains (folders, models, dictionary, search), and each tool appears to earn its place by addressing specific operations. However, it borders on being heavy, which might overwhelm agents if not well-organized.
The tool surface provides complete CRUD/lifecycle coverage for key domains: folders (create, get, update, move, delete), models (create, get, update, move, export, publish, revisions), and dictionary entries (create, get, update, delete, categories). It includes essential utilities like authentication, search, and root folder access, with no obvious gaps that would cause agent failures in typical workflows.
Related MCP Connectors
Connect AI agents to Process Street workflows, tasks, runs, data sets, and operational records.
Enables AI assistants to retrieve event data and execute event management operations in Nunify.
Connect AI assistants to Stellary projects, boards, documents, and governed agent workflows.
Give AI agents 30,000+ safe, token-optimized actions across Workday, SAP, Oracle + hundreds more.
Related MCP Servers
- AlicenseBqualityBmaintenanceExposes over 300 Operaton BPM REST operations as tools for AI agents to interact with the Operaton engine. It enables managing process deployments, instances, user tasks, and decision tables through natural language commands.105238 npmApache 2.0
- AlicenseBqualityAmaintenanceEnables AI assistants to read, create, and modify SAP BW/4HANA modeling objects via the internal REST API, including aDSOs, InfoObjects, transformations, DTPs, queries, and more.21173 npm85MIT
- AlicenseAqualityDmaintenanceConnects AI agents to SAP BTP platform APIs for service discovery, instance management, and destination queries via natural language.524 PyPI1MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to create and manage one BPMN 2.0 diagram at a time, including Mermaid conversion, validation, layout, persistence, and XML or SVG export.27760 npmMIT