@mclawnet/mcp-server
v0.1.4
Published
MCP server exposing ClawNet capabilities (skills, memory, evolution, tasks, inbox) to any Model Context Protocol client.
Readme
@mclawnet/mcp-server
MCP server exposing ClawNet capabilities (skills, memory, evolution, tasks, inbox) to any Model Context Protocol client.
The binary clawnet-mcp is registered in package.json#bin and launched by
the agent host (or any external MCP client).
Tool groups
- Skill — discover and execute skills from the local skill manager.
- Memory — read/write the agent memory store.
- Evolution — skill evolution telemetry helpers.
- Task & Inbox — first-class task graph + inter-instance messaging (added in 0.1.4, see below).
Task & Inbox tools
Backed by @mclawnet/task. All tools are project-scoped via a required
workDir argument (absolute path to the project working directory). See
the design doc docs/plans/2026-04-25-task-as-first-class-design.md.
| Tool | Description |
| --- | --- |
| task_create | Create a task in the project task store. |
| task_get | Fetch a task by id. |
| task_list | List tasks with optional swarmId / status / owner filters. |
| task_set_status | Update status; cancel auto-unlinks edges and fans out inbox notifications to downstream owners. |
| task_set_owner | Set or clear (null) the owner instance id. |
| task_add_comment | Append an idempotent comment (auto-uuid if id omitted). |
| task_link | Add a blockedBy / blocks edge; rejects self-link, cycles, missing tasks. |
| task_unlink | Remove an edge in both directions; no-op if absent. |
| task_create_from_message | Spin a task off an inbox message; records origin_message system comment. |
| task_briefing | Per-instance situation summary (actionable / awareness / counters / warnings). |
| lead_briefing | Queen-facing buckets: assign_owner, assign_reviewer, clarify, repair_dependencies, lead_owned. |
| member_briefing | Boot briefing for a worker/queen with hardcoded boot rules + bootstrap context. |
| message_send | Durably write an inbox message between two instances within a swarm. |
Fan-out
When a task transitions to a terminal state (e.g. done or cancelled),
the server walks its blocks edges and delivers an inbox message via
message_send to each downstream task's owner — so newly unblocked work
surfaces without the recipient polling.
