Roder
Capabilities

MCP integration

MCP is the language-agnostic extension path for tools that should run outside the Roder process. The legacy implementation already proved the host behavior; the Rust roadmap tracks the parity work for MCP and LSP capabilities.

Target model

  • Attach MCP servers to a session or app-server client.
  • Discover tool schemas through the MCP handshake.
  • Register MCP tools into the same ToolRegistry as native tools.
  • Route calls through Roder policy, approval, event, and result handling.
  • Terminate session-scoped server processes when the session closes.

Naming

MCP tools should be namespaced so provider-visible names do not collide with built-ins or native extension tools. 

mcp.<server-name>.<tool-name>

When to use MCP vs native extensions

  • Use MCP when you need process isolation, language independence, or a tool that ships separately.
  • Use a native Roder extension when you need direct Rust integration, tighter lifecycle control, or hot-path performance.