@meta
  v: 1
  route: /docs/mcp-and-harness
  generated: 2026-06-17T00:00:00Z
  ttl: 1d

@intent
  purpose:    Run Roundtable as an MCP server and auto-wire it into coding harnesses
  audience:   developer, ai-agent
  capability: serve-mcp, integrate-harness

@state
  mcp_command: roundtable mcp serve
  transport: JSON-RPC over stdio
  exposed_tool: roundtable(question, heads?, rounds?, research?) -> markdown transcript
  mcp_config: {"command": "roundtable", "args": ["mcp", "serve"]}
  install_command: roundtable install (idempotent; backs up existing config first)
  supported_harnesses[4]{harness,wired}:
    Claude Code,The Roundtable skill (~/.agents/skills/roundtable/) and the MCP server
    Cursor,MCP server entry in ~/.cursor/mcp.json
    Codex CLI,[mcp_servers.roundtable] in ~/.codex/config.toml
    generic,Prints the MCP JSON for you to paste anywhere

@actions
  - id: serve_mcp
    method: GET
    href: https://roundtable.sh/docs/mcp-and-harness
    command: roundtable mcp serve
  - id: print_mcp_config
    method: GET
    href: https://roundtable.sh/docs/mcp-and-harness
    command: roundtable mcp config
  - id: wire_all
    method: GET
    href: https://roundtable.sh/docs/mcp-and-harness
    command: roundtable install --all

@context
  > The MCP server is a subcommand of the same binary — no separate package. Any harness that
  > speaks the Model Context Protocol can call the council as a tool. `roundtable install` detects
  > installed harnesses and wires each idempotently, never clobbering your settings.

@nav
  self:      /docs/mcp-and-harness.agent
  parents:   [/]
  peers:     [/docs/get-started.agent, /docs/how-it-works.agent, /docs/the-heads.agent, /docs/cli-reference.agent, /docs/agents.agent]
  drilldown: /docs/agents.agent