🚀 EDDI 6.5.0

19 LLM providers, knowledge bases that crawl your site and read your files, and conversations that follow compatible agent versionsWhat's new

Managed Cloud Get Started
All integrations
Agent protocolsStreamable HTTP

MCP Server

Control EDDI from Claude Desktop, Cursor, VS Code and other MCP clients. EDDI exposes 84 MCP tools over Streamable HTTP for conversations and administration.

ConfigurationDocs ↗

What you get

  • 84 tools: list and talk to agents, create and deploy them, manage groups, schedules and more
  • A single endpoint, /mcp, using Streamable HTTP
  • Works with clients that speak HTTP directly and, through a bridge, with stdio-only clients
  • Role-based access when authentication is on

How it works in EDDI

  1. Run EDDI. The MCP endpoint is http://localhost:7070/mcp.
  2. Add EDDI to your MCP client. HTTP-capable clients use the URL directly.
  3. For stdio-only clients such as Claude Desktop, use the mcp-remote bridge as shown.
  4. Ask the assistant to list agents, start a conversation or create an agent. The documented flow is list_agents, create_conversation, talk_to_agent.
  5. With OIDC on, give the client a bearer token.

Configuration

Taken from the EDDI documentation. Placeholders such as your-agent-id are yours to replace.

Clients with HTTP transportFor clients with native HTTP transport.
{
  "mcpServers": {
    "eddi": {
      "url": "http://localhost:7070/mcp"
    }
  }
}
stdio-only clients (for example claude_desktop_config.json)For stdio-only clients. On Windows, wrap the command with cmd /c if npx is not on the PATH.
{
  "mcpServers": {
    "eddi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://localhost:7070/mcp"]
    }
  }
}

Governance

  • Write tools such as setup_agent and create_api_agent need the eddi-editor role.
  • The MCP create_api_agent tool deliberately cannot set an approval gate. Provisioning a gated agent goes through REST with eddi-admin.
  • Group phases that wait for approval can be approved through MCP as well as the Manager, REST and Slack, and every decision is audited.

Good to know

  • Production start refuses to run with OIDC off unless you opt out, and an opted-out instance leaves /mcp open to anyone who can reach the port.
Get startedDocs ↗

Related integrations

Agent protocolsMCP ClientGive EDDI agents the tools of external MCP servers. A server's tools become the agent's tools, behind the same approval gates and audit trail as every other tool.Agent protocolsA2AExpose EDDI agents to other agents through Agent Cards and JSON-RPC, and use remote A2A agents as tools inside your own agents.Enterprise systemsOpenAPITurn any REST API with an OpenAPI 3.0 or 3.1 description into an agent with tools, without writing code, and gate the consequential calls behind human approval.

Configuration and behavior on this page follow the EDDI documentation, checked on 2026-10-14. Field names and defaults can change between releases, so confirm them in the docs for your version.