Task Manager MCP Server
MCP server with seven tools for listing, creating and advancing tasks stored in ~/.config/robos/tasks/tasks.json.
packages/task-manager-mcp
Task Manager MCP gives an agent a simple local task list. Tasks live in ~/.config/robos/tasks/tasks.json. On first run the file is created with three sample tasks (TASK-101 to TASK-103).
Tools
| Tool | What it does |
|---|---|
robos_tasks_list |
List tasks, optionally filtered by status, assignee or epic. |
robos_tasks_get |
Return one task by id, or an error if it does not exist. |
robos_tasks_create |
Create a task (title, priority, type, assignee). Without an id it generates one like TASK-123. |
robos_tasks_update |
Merge fields into a task. |
robos_tasks_advance_workflow |
Move a task along TODO, IN_PROGRESS, REVIEW, DONE. |
robos_tasks_add_comment |
Add a timestamped comment. |
robos_tasks_log_hours |
Add to the task’s logged hours. |
Resources: robos://task-manager/tasks/active (in-progress tasks) and robos://task-manager/tasks/all.
The console window
Task Manager MCP Server Console shows task counts per status, + Create MCP Task and Advance Active Workflow buttons, and a protocol trace of the calls. The server is created without an HTTP port, so it only registers itself in ~/.config/robos/mcp/servers.json. The MCP Router has its own implementation of the same tool names that works on the same tasks.json file.
Run it with npm start in packages/task-manager-mcp; there is no .desktop launcher. npm test runs node --test. To connect Jira, GitHub or Linear to RobOS, see Task Servers.
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 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.
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.