Parent: TechDevGroup/devagentic#203.

Gap

mcp_serve.py registers only canvas tools (_register_canvas_tools for hermes #56). Devagentic mutations are not exposed as MCP-registered native tools, so workers still need to shell out to python api.py — violating NousResearch#203 §1.2.

What is needed

Add MCP tool wrappers for:

• querySilo(silo, query, ...) — read graph state
• writeDoc(kind, body, tags, user_id?) — write a doc node
• confer(silos, prompt, ...) — kick off a confer-loop
• forkContext(parent_id, ...) — branch context
• assertOutput(...) — output assertion
• patchArtifact(...) — in-place artifact edit
• Plus any other resolvers devagentic exposes per test: add unit tests for trajectory_compressor NousResearch/hermes-agent#203 §1.2

Acceptance

• All listed tools registered under mcp_serve.py alongside _register_canvas_tools.
• Per-tool unit tests covering MCP serialization + devagentic call shape.
• Worker can invoke writeDoc(...) etc. as a native MCP tool without shelling out.

Notes

• Base URL + X-User-Id auto-bind already exist in plugins/model-providers/devagentic-local/ — reuse that pattern.
• Coordinate canonical tool list with devagentic's resolver layer.