The engine
that runs your skills.
The MMC MCP Server reads your SKILL.md files from GitHub, executes the business logic, and connects to your tools — all without sending your data to any MMC database.
Three layers. One standard.
The MMC architecture separates authoring (proprietary Workbench), logic storage (open SKILL.md standard), and execution (MCP Server) into three independent, auditable layers.
Every layer is
independently auditable.
What happens when
your AI calls a skill.
tool: slice-1-receive-request
role: claims-processor
source: your-org/mmc-skills
file: slice-1-receive-request.SKILL.md
Scenario A: invalid inputs → error
Scenario B: valid → log event
log-event-to-bus. The bus then dispatches to the next skill in the flow — creating a fully traceable, step-by-step audit trail of every AI decision.Your tools. Your infrastructure.
The MCP Server connects to your existing business systems via secure connectors. All reads and writes happen from infrastructure you control — never routed through MMC servers.
A connector is an ordinary MCP server, written in any language by your team or your implementation partner. Register it in your deployment’s configuration and every step in your workflow can call its tools. You own its code: version it, test it and update it on your own schedule by pointing your deployment at the new version — no change to the engine, and no MMC release to wait for.
Every execution is logged to a local event store in your deployment, queryable via get-session-events and the events dump. You get bottleneck, error and outcome visibility — it lives in your infrastructure, not an MMC database.
Runs on
your infrastructure.
The MCP Server is a standalone process that runs where you decide — your cloud, your VPC, your region. Your business logic stays in your own GitHub repository, readable and version-controlled. You keep your models, your data and your repository.
Your procurement team already approved GitHub. There is no MMC database to review. No sensitive data touches our infrastructure.
- Claude Desktop
- Gemini CLI
- OpenAI Codex
- Any MCP-compatible agent
Your logic. Your infrastructure.
Keep your models and data.
The MCP Engine runs in your environment and executes the SKILL.md files in your own repository. Start with the Workbench to generate your first SKILL.md, then connect the engine to any AI agent.
Works with Claude, Gemini & any MCP-compatible agent · Your GitHub, your data