1.2 KiB
1.2 KiB
2026-02-23 Session Notes
MCP Server Exposure for Signet Daemon
The user requested exposing the Signet daemon as an MCP (Model Context Protocol) server to all available harnesses (Claude Code, OpenCode, and OpenClaw) so they can access daemon endpoints natively as tools instead of invoking skills directly.
Scope & Requirements
The task requires:
- Researching the daemon's existing HTTP server structure in
packages/daemon/src/daemon.ts - Understanding MCP server patterns and implementations across all three harnesses
- Identifying which daemon endpoints should become MCP tools (memory recall/remember, skills, secrets, documents, config, diagnostics, repair)
- Designing an extensible and scalable approach
- Acknowledging that OpenClaw handles MCP differently than Claude Code and OpenCode
Research Initiated
An Explore agent was launched to thoroughly investigate:
- The full Hono server setup and route registrations
- All API route handler files and their organization
- Key endpoints valuable as MCP tools
- Current authentication and CORS mechanisms
- The session tracker and runtime path system
The session entered plan mode to structure the investigation before implementation.