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.
packages/dev-tools-mcp
This package is an MCP server plus a console window. The idea is that an agent can ask what tooling a machine has and request more. The current code keeps a catalog file and nothing more.
robos_devtools_install sets installed: true on a catalog entry and replies “Successfully provisioned”. It does not download or run anything. robos_devtools_check reports the flag in the file, not whether the binary is on your PATH.
Tools and resources
| Tool | What it does |
|---|---|
robos_devtools_list |
Returns the whole catalog with each entry’s installed flag and version |
robos_devtools_check |
Looks up one tool id; reports “not in the RobOS tool catalog” for unknown ids |
robos_devtools_install |
Marks a tool installed. An unknown id is added as a “Custom CLI” entry at version 1.0.0 |
robos_devtools_uninstall |
Marks a tool not installed; errors on an unknown id |
Resources: robos://dev-tools-mcp/devtools/installed and robos://dev-tools-mcp/devtools/available.
The default catalog has Docker Engine, Kubernetes CLI (kubectl), GitHub CLI (gh), K9s, HashiCorp Terraform and AWS CLI v2. Docker, kubectl, gh and K9s start as installed, with the version numbers written in server.js.
Console window
The window title is “RobOS Dev Tools MCP Server Console”. It shows counters (installed, catalog size, tools, pending), the tool registry, quick buttons (Check Docker, Install Terraform) and a Live Dev Tools MCP Protocol Trace with Clear Trace. It calls the service over Electron IPC.
Data and registration
- Catalog:
~/.config/robos/devtools/tools.json, written on first run. - On start the server records its tool and resource names in
~/.config/robos/mcp/servers.jsonunder the iddevtools. It opens no port unless aportoption is passed.
electron packages/dev-tools-mcp
npm test in the package runs node --test. Source: packages/dev-tools-mcp.
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.
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 Router
Single MCP endpoint that lists the tools of the servers in the registry and routes tool calls to them, with built-in fallbacks.
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.