Management MCP
https://utils.demo.clace.io/_openrun/mcpLets an AI client operate OpenRun as you: list and create apps, promote, manage services and bindings, run syncs. Enabling needs:
- ✓ RBAC enforcement - always on
- ✓ HTTPS listener or a trusted TLS proxy - HTTPS listener on
- ✓ External URL - https://utils.demo.clace.io
Additional settings
App actions MCP
https://utils.demo.clace.io/_openrun/app_mcpConnect a client - Claude Code, Codex, any MCP client
Pick the login the client connects with and, optionally, an app path glob to narrow the view. Without a login only apps with auth none are visible. The openrun_status tool reports who is connected and what the view holds.
Apps: a path glob like /team/** or example.com:/**; empty means all
claude mcp add --transport http openrun-apps "https://utils.demo.clace.io/_openrun/app_mcp"
codex mcp add openrun-apps --url "https://utils.demo.clace.io/_openrun/app_mcp"
https://utils.demo.clace.io/_openrun/app_mcp
Your apps with actions
| App | Actions | Own endpoint | |
|---|---|---|---|
| /weather | 3 actions | actions · detail | |
| utils.demo.clace.io:/dict | 1 action | actions · detail | |
| utils.demo.clace.io:/list_files | 1 action | actions · detail | |
| utils.demo.clace.io:/num_lines | 1 action | actions · detail |
Each app also serves its actions on its own /mcp url with the app's own login; setting an app's MCP to disable (its edit form) removes it from every tool list.