Harper's MCP server and the schema generation it shares with OpenAPI. This epic gives that work a live parent.
Why this exists
#1349 (MCP server: complete the protocol surface) was the de facto MCP epic, and it is closed as completed while still holding three open children — #1107, #1368, and #1548. Open work under a closed parent doesn't show up in any epic-progress view, so those are adopted here along with the MCP issues that were never parented at all.
Scope
In: the MCP protocol surface (sessions, subscriptions, streaming, protocol-era handling), tool and resource registration, and the schema type mapping shared between MCP and OpenAPI.
Out: the operations API itself (#1681) — MCP exposes it, but defects in the operations are that epic's. General component-authoring concerns (#1678) unless MCP-specific.
Created during backlog triage; the child issues keep their own priorities and milestones.
Harper's MCP server and the schema generation it shares with OpenAPI. This epic gives that work a live parent.
Why this exists
#1349 (
MCP server: complete the protocol surface) was the de facto MCP epic, and it is closed as completed while still holding three open children — #1107, #1368, and #1548. Open work under a closed parent doesn't show up in any epic-progress view, so those are adopted here along with the MCP issues that were never parented at all.Scope
In: the MCP protocol surface (sessions, subscriptions, streaming, protocol-era handling), tool and resource registration, and the schema type mapping shared between MCP and OpenAPI.
Out: the operations API itself (#1681) — MCP exposes it, but defects in the operations are that epic's. General component-authoring concerns (#1678) unless MCP-specific.
Created during backlog triage; the child issues keep their own priorities and milestones.