Skip to content

epic(m3): surfaces — REST, CLI, and MCP over the SDK #24

Description

@JArmandoAnaya

Goal

Make the kernel operable from the outside through its three sibling clients — REST API
(with token auth, public contract), CLI, and MCP — all thin wrappers over the SDK, none
importing another (enforced by import-linter).

Exit criterion

The full M1+M2 flow executed three ways: (a) curl with a bearer token, (b) the CLI,
(c) Claude Code over MCP stdio.

Workstreams

  • WS-1 Auth (tokens end to end)
  • WS-2 REST endpoints for the full cycle
  • WS-3 Contract quality: errors, OpenAPI drift gate, TS client generation
  • WS-4 CLI: visionset ui + flow commands
  • WS-5 MCP tools + real-agent validation

Constraints

  • Every capability lands in the API and is evaluated as an MCP tool in the same PR
    (parity rule, vision doc principle 8) from this milestone on.
  • No logic in the server "because it was faster there": surfaces wrap existing, tested
    services only.

Tracked issues

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    apivisionset.server — REST API and OpenAPI contractclivisionset.cli — Typer CLIepicMilestone/phase epic — tracks a group of issuesm3M3 — Surfaces: API + CLI + MCP (0.0.1-alpha.3)mcpvisionset.mcp — MCP server and tools

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions