MCP Router

Single MCP endpoint that lists the tools of the servers in the registry and routes tool calls to them, with built-in fallbacks.

packages/robos-mcp-router

The router lets an agent such as Claude Code connect to one MCP server and see the tools of the other RobOS servers. Treat it as an early implementation: parts of it return canned data, described below.

Connect an agent

The package provides the command robos-mcp-router (cli.js), which speaks JSON-RPC over stdin and stdout. Print a ready-made client config with:

node packages/robos-mcp-router/cli.js --claude-config

The output registers a server named robos that runs node /usr/local/share/robos/robos-mcp-router/cli.js --stdio, so the path assumes a RobOS install. The Router Console window has a Claude Config button that shows the same JSON.

How routing works

  • tools/list and resources/list merge the entries in ~/.config/robos/mcp/servers.json, which servers built with MCP Server Framework write on start. If that file is empty or missing, the router lists five built-in sample servers (task-manager, ekgraph, kube-studio, rest-client, workspace-manager) instead.
  • tools/call finds the server that owns the tool name. If that server has an HTTP endpoint, the request is forwarded. If the endpoint is missing or the request fails, the router runs its own handler. Because of this fallback, a successful response does not prove the target server answered.
  • Local handlers: robos_tasks_* tools read and write ~/.config/robos/tasks/tasks.json. robos_kube_deploy and robos_kube_get_pods run kubectl, and return sample output if it fails. robos_rest_send_request sends a real HTTP request, and on a connection error returns a hard-coded sample response. robos_ekgraph_* tools always return a fixed sample result. Any other tool name gets a generic SUCCESS echo.
  • resources/read returns a placeholder object, not the resource’s content.

The console window

RobOS Unified MCP Router Console shows the number of servers, aggregated tools and resources, and a dispatch log. Test Task Manager Route sends a sample call. Run it with npm start in packages/robos-mcp-router; there is no .desktop launcher. npm test runs node --test.

More in Agent Services & MCP Servers

Agent Autoconfig Writes MCP configuration and instruction files so Claude Code, Gemini, Copilot and Cursor all point at the RobOS MCP router. Agent Daemon (agentd) Keeps a registry of sub-agent sessions, each with its own home directory and environment, behind a Unix socket and a small window. Agent Profile Daemon Creates short-lived agent profiles with their own home directory (tmpfs when run as root) and runs commands with that home and environment. Agent Session Library Node.js client for the agentd socket, plus a small demo window and a simulated test-driven-development runner. CI Monitor MCP Server An MCP server that lets agents list Buildkite builds and read failed-job logs, backed by the connection set up in CI Monitor. Dev Tools MCP Server An MCP server with a small catalog of developer CLI tools; "install" and "check" read and write a JSON file and do not touch the system. Engineering Knowledge Graph MCP Server An MCP server that lets agents search and edit a small node store, query and propose changes to the SDLC graph, and look up schema types. IDE Bridge MCP Server An MCP server that forwards IDE commands (open file, breakpoints, run configurations, refactorings) to the RobOS IntelliJ plugin on port 63343. MCP Server Framework Node.js library for building small Model Context Protocol servers, with an HTTP and a stdio transport and a shared registry file. RobOS CLI Tools Four shell scripts for scripts and agents: send a notification, set the active task, append to the work journal, and emit or read events. System MCP Server MCP server with six tools for preferences, notifications, a tool inventory, file-name search and the active task, backed by a JSON file with sample data. Task Manager MCP Server MCP server with seven tools for listing, creating and advancing tasks stored in ~/.config/robos/tasks/tasks.json. Workspace Manager MCP Server MCP server with six workspace tools, backed by a JSON file of sample workspaces. Several tools return canned results and do not run anything.