Reach · 08.07
The MCP Plane Is Bilateral
Agentis both consumes external MCP servers and publishes its own workflows as JSON-RPC 2.0 Streamable-HTTP tools — one registry, many projections.
Consuming: any MCP server becomes an agent tool by name
Agentis has always been able to reach an external MCP server over REST, but that alone doesn't put its tools in front of an agent's own reasoning loop. McpToolBridge closes that gap: it resolves the MCP servers registered to a workspace, lists and caches their tools, and offers each one to the agent loop and chat orchestrator by a namespaced id — mcp__<serverSlug>__<toolName> — so a bridged tool can never collide with a built-in platform tool and is always obviously external in logs. A server tagged as granting a specific RAL affordance (a computer-use MCP server, for instance) extends what an agent can actually do, not just what it can call.
Publishing: your workflows are someone else's MCP tools
The other direction: Agentis publishes its own workflows as JSON-RPC 2.0 Streamable-HTTP tools any external MCP client can call — mount once, and a published workflow projects simultaneously as a deterministic workflow node and a live agent tool. "Bilateral" isn't a marketing word here; it's the literal shape of the plane.