aris-mcp
Integrates with Camunda to reconcile ARIS process models with Camunda workflows via a knowledge graph, enabling alignment between business process modeling and execution.
Click on "Install 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., "@aris-mcpget model 'Order to Cash' with its EPC structure"
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.
aris-mcp
Software AG ARIS REST API + MCP Server + A2A Server for Agentic AI.
aris-mcp connects the agent ecosystem to an ARIS tenant (ARIS Connect / ARIS
Enterprise / ARIS Cloud). It is the inbound and outbound bridge for the
agent-utilities Knowledge Graph's Camunda + ARIS ↔ KG integration:
Inbound — the KG ARIS extractor (
enrichment/extractors/aris.py) consumes this client to lift ARIS models + their EPC structure (functions → BusinessTask, rule operators → gateways, events collapsed, connections → FLOWS_TO) into the canonical ArchiMate ontology, where they reconcile with Camunda/Egeria viaALIGNED_WITHand are reasoned over in OWL/RDF.Outbound — the KG process-intelligence writeback (
enrichment/process_writeback.py) usesset_model_attributesto write akg_intelligenceattribute back onto ARIS models (gated byARIS_ENABLE_WRITE).
Available MCP Tools
The table below is auto-generated from the live server — do not edit by hand.
Condensed action-routed tools (default — MCP_TOOL_MODE=condensed)
MCP Tool | Toggle Env Var | Description |
|
| Work with ARIS models and their EPC structure. |
|
| Write attributes on a single ARIS object. |
Verbose 1:1 API-mapped tools (MCP_TOOL_MODE=verbose or both)
MCP Tool | Toggle Env Var | Description |
|
| Get a single model's metadata (including its attributes). |
|
| Get a model's attributes (used for writeback idempotency read-back). |
|
| List the directed control-flow connections between a model's objects. |
|
| List the EPC objects (functions/events/rule operators) of a model. |
|
| List models in the tenant/database (process + architecture). |
|
| Write/update attributes on a model (e.g. the |
|
| Write/update attributes on a single object. |
2 action-routed tool(s) (default) · 7 verbose 1:1 tool(s). Each is enabled unless its <DOMAIN>TOOL toggle is set false; MCP_TOOL_MODE selects the surface (condensed default · verbose 1:1 · both). Auto-generated — do not edit.
Writes require
ARIS_ENABLE_WRITE=True.
Related MCP server: Letta MCP Server
Environment Variables
Package environment variables
Variable | Example | Description |
|
| ARIS REST base URL (tenant API root). Default follows the ARIS Connect ABS layout. |
|
| Verify TLS (set False for self-signed / homelab tenants) |
| — | 1. OAuth2 client-credentials (preferred for ARIS Cloud / Connect) |
| — | |
| — | |
| — | |
| — | 2. Static bearer token (alternative to OAuth) |
| — | 3. HTTP basic auth (alternative) |
| — | |
| — | e.g. {"models":"v2/repository/models","model_objects":"v2/models/{model_id}/objects"} |
|
| Allow (gated) attribute writes back onto ARIS models (KG writeback) |
|
| stdio, streamable-http, or sse |
|
| |
|
| |
|
| Tool surface: condensed, verbose, or both |
| — | Comma-separated tool / tag allow/deny lists |
| — | |
| — | |
| — | |
|
| |
|
| |
|
| The action-routed ARIS tools (aris_model, aris_object) share this toggle. |
|
| |
| — | |
| — | |
| — | |
| — | |
|
| |
|
| |
| — |
Inherited agent-utilities variables (apply to every connector)
Variable | Example | Description |
| — | Outbound MCP auth ( |
| — | OIDC client id (service-account auth) |
| — | OIDC client secret (service-account auth) |
|
| URL of the MCP server the agent connects to |
|
| LLM provider for the agent |
|
| Model id for the agent |
|
| Serve the AG-UI web interface |
30 package + 7 inherited variable(s). Auto-generated from .env.example + the shared agent-utilities set — do not edit.
Every variable the server reads, grouped by concern.
Connection & Credentials
Variable | Purpose | Default |
| ARIS REST base URL (tenant API root) |
|
| verify TLS |
|
| OAuth2 client-credentials (preferred) | — |
| static bearer token (alt to OAuth) | — |
| HTTP basic (alt) | — |
| JSON overriding REST path templates per tenant | — |
| allow attribute writes |
|
Tenant differences. ARIS deployments vary (Connect ABS portal vs the public ARIS API; on-prem vs Cloud). The defaults follow the common ARIS Connect ABS REST layout. If your tenant's paths differ, set
ARIS_PATHS_JSON, e.g.{"models":"v2/repository/models","model_objects":"v2/models/{model_id}/objects"}.
MCP server / transport
Variable | Description | Default |
|
|
|
| Bind host (HTTP transports) |
|
| Bind port (HTTP transports) |
|
| Tool surface: |
|
| Comma-separated tool allow/deny list | — |
| Comma-separated tag allow/deny list | — |
| Verbose logging |
|
| Unbuffered stdout (recommended in containers) |
|
Tool toggles
The action-routed tools can be disabled via their toggle env var (set to false):
ARISTOOL (see the Available MCP Tools table above).
Telemetry & governance
Variable | Description | Default |
| Enable OpenTelemetry export |
|
| OTLP collector endpoint | — |
| OTLP auth keys | — |
| OTLP protocol (e.g. | — |
| Authorization mode: |
|
| Embedded policy file |
|
| Remote Eunomia server URL | — |
Agent CLI (full [agent] runtime only)
Variable | Description | Default |
| URL of the MCP server the agent connects to |
|
| LLM provider (e.g. |
|
| Model id (e.g. |
|
| Serve the AG-UI web interface |
|
Installation
Install the slim
[mcp]extra. Installaris-mcp[mcp]— the MCP-server extra that pulls only the FastMCP / FastAPI tooling (agent-utilities[mcp]). It deliberately excludes the heavy agent runtime (the epistemic-graph engine,pydantic-ai,dspy,llama-index,tree-sitter), souvx/container installs are dramatically smaller and faster. Use the full[agent]extra only when you need the integrated Pydantic AI agent.
Pick the extra that matches what you want to run:
Extra | Installs | Use when |
| Slim MCP server only ( | You only run the MCP server (smallest install / image) |
| Full agent runtime ( | You run the integrated agent |
| Everything ( | Development / both surfaces |
# MCP server only (recommended for tool hosting — slim deps)
uv pip install "aris-mcp[mcp]"
# Full agent runtime (Pydantic AI + epistemic-graph engine)
uv pip install "aris-mcp[agent]"
# Everything (development)
uv pip install "aris-mcp[all]" # or: python -m pip install "aris-mcp[all]"Container images (:mcp vs :agent)
One multi-stage docker/Dockerfile builds two right-sized images, selected by --target:
Image tag | Build target | Contents | Entrypoint |
|
|
|
|
|
|
|
|
docker build --target mcp -t knucklessg1/aris-mcp:mcp docker/ # slim MCP server
docker build --target agent -t knucklessg1/aris-mcp:latest docker/ # full agentdocker/mcp.compose.yml runs the slim :mcp server; docker/agent.compose.yml runs the
agent (:latest) with a co-located :mcp sidecar.
Knowledge-graph database (epistemic-graph)
The full agent ([agent] / :latest) embeds the epistemic-graph engine (pulled in
transitively via agent-utilities[agent]). For production — or to share one knowledge graph
across multiple agents — run epistemic-graph as its own database container and point the
agent at it instead of embedding it. Deployment recipes (single-node + Raft HA), connection
config, and the full database architecture (with diagrams) are documented in the
epistemic-graph deployment guide.
The slim [mcp] server does not require the database.
Run
aris-mcp # stdio (default)
aris-mcp --transport streamable-http --host 0.0.0.0 --port 8000Deployment
stdio —
uv run aris-mcp(seemcp_config.json).streamable-http —
aris-mcp --transport streamable-http --port 8000.local container — build from
docker/and run with the env above.remote — point your client at
http://aris-mcp.arpa/mcp.
Deploy with agent-os-genesis
This package can be provisioned for you — skill-guided — by the agent-os-genesis
universal skill (its single-package deploy mode): it picks your install method, seeds
secrets to OpenBao/Vault (or .env), trusts your enterprise CA, registers the MCP
server, and verifies it — the same machinery that stands up the whole Agent OS, narrowed
to just this package. Ask your agent to "deploy aris-mcp with agent-os-genesis".
Install mode | Command |
Bare-metal, prod (PyPI) |
|
Bare-metal, dev (editable) |
|
Container, prod | deploy |
Container, dev (editable) | deploy |
Secrets are read-existing + seeded via vault_sync — you are only prompted for what's missing.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Knuckles-Team/aris-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server