Skip to main content
Endpoint: /runtime/mcp
Permission: Use (odin:use) — consent label Use your agents and tools Runtime turns what already exists in EKB into named MCP tools. Draft / unpublished work is never exposed — publishing is what makes custom tools available over MCP.

​
Prerequisites

  • Consent to Use your agents and tools for this client
  • Access to the project(s) whose agents, tools, KB, or smart tables you want to use
  • Published workflows / custom tools if you need run_* tools

​
Tools the client sees

​
Always present

Use search_knowledge for looking up facts in documents. Use an ask_<agent> tool when you want an agent to reason over those results.

​
Dynamic tools (per project)

Naming notes:
  • Agent and tool names are slugified for MCP (punctuation normalized)
  • With multiple projects and no pin, names may include a project qualifier
  • Tool lists can be large; pin a project when you know the target
Every ask_* response includes a chat_id. Pass it back on the next call to continue the same conversation; omit it to start fresh.

​
Pin a project

Send this header from your MCP client config:
Discover ids with list_odin_projects if you do not already know them.

​
Publishing and visibility

Runtime does not grant extra visibility. Access Tags and project membership still filter what search and agents can return.

​
When to use Runtime

  • “Ask our support / HR / ops agent from Claude”
  • “Run this published workflow with these inputs”
  • “Search the KB” or “pull rows from a smart table”
  • Any client that should use EKB without permission to change configuration

​
Tips

  • Publish workflows before expecting them as run_* tools
  • Prefer Runtime-only connections on laptops and assistants that must not edit agents
  • Prefer ask_* when you want judgment; prefer search_knowledge / query_smart_table for direct lookup
  • Keep conversations coherent by reusing chat_id

​
Troubleshooting