MCP Tools¶
Emakin exposes Model Context Protocol (MCP) tools through separate endpoints for runtime work and development work. Connect an MCP client to the surface that matches the task.
Choose the MCP Surface¶
| Surface | Endpoint | Use for |
|---|---|---|
| User | https://mydomain.emakin.com/mcp | Runtime, end-user workflow operations such as reading or completing work items, starting available processes, and working with cases, identities, and files. |
| Development | https://mydomain.emakin.com/mcp/development | Process-definition and development work, including inspecting or changing process definitions, forms, scripts, and platform documentation. |
Replace mydomain.emakin.com with the HTTPS address of the Emakin application.
Connection Requirements¶
Before connecting a client, make sure that:
- the selected MCP surface is enabled for the application in Host Administration; see MCP Modes
- the client uses HTTPS and authenticates with an Emakin bearer token
- the token belongs to a user with access to the target tenant and the required Emakin permissions
For creating and managing bearer tokens, see REST Services. MCP uses the caller's existing Emakin permissions.