MCP Servers

Documentation Index

Fetch the complete documentation index at: https://docs.idun-group.com/llms.txt

Use this file to discover all available pages before exploring further.

​

How it works

1. Register MCP servers in the admin panel or YAML config with transport settings and connection details
2. The engine discovers tools from each configured MCP server at startup
3. Agents invoke tools during conversations as needed, with results passed back for response generation

​

Transport types

​

Configuration example

• Admin UI
• YAML config

1

Open the MCP admin page

Navigate to /admin/mcp/ in the running standalone. The catalog at the top groups MCP servers by transport: Streamable HTTP, SSE, WebSocket, and stdio. Existing servers are listed below with their transport, endpoint, and status.

2

Add an MCP server

Click the transport card you want and fill in the form: a unique name, the URL (or command and args for stdio), optional headers. The Enabled toggle lets you keep a server configured but skipped at startup.

3

Save and verify

Save; the reload pipeline re-instantiates the engine with the new MCP registry. Click the wrench icon next to a server to probe it and list the tools it advertises. The probe doubles as a connection check.

Tools are discovered at engine boot and made available to your agent via get_langchain_tools() / get_adk_tools().

config.yaml

mcp_servers:
  - name: fetch
    transport: stdio
    command: docker
    args: ["run", "-i", "--rm", "mcp/fetch"]

  - name: filesystem
    transport: stdio
    command: npx
    args: ["-y", "@modelcontextprotocol/server-filesystem", "/data"]
    env:
      ALLOWED_DIRECTORY: /data

  - name: custom-api
    transport: streamable_http
    url: https://mcp.example.com/api
    headers:
      Authorization: "Bearer ${MCP_API_TOKEN}"

​

Integration approaches

​

Framework integration

from idun_agent_engine.mcp import get_adk_tools

idun_tools = get_adk_tools()

​

Next steps