MCP Integration

MCP Integration

Okto Pulse ships its own MCP (Model Context Protocol) server. Point any MCP-aware agent at it, and the agent gets the full board API — 150+ tools spanning ideations, refinements, specs, sprints, cards, validations, analytics, and agents themselves.

Configuration

Pulse generates a starter .mcp.json on okto-pulse init. Minimal form:

{
  "mcpServers": {
    "okto-pulse": {
      "url": "http://127.0.0.1:8101/mcp?api_key=dash_xxx"
    }
  }
}

Drop that file next to your agent’s config.

Tested clients

• Claude Code — add the .mcp.json to your project root.
• Cursor — Settings → MCP → Add server.
• Windsurf — Settings → Cascade → MCP.
• Custom orchestrators — any MCP client that speaks streamable HTTP.

Sample tool surface

okto_pulse_list_my_boards
okto_pulse_create_ideation
okto_pulse_derive_spec_from_refinement
okto_pulse_create_sprint
okto_pulse_assign_tasks_to_sprint
okto_pulse_submit_spec_validation
okto_pulse_submit_task_validation
okto_pulse_ask_spec_question
okto_pulse_add_test_scenario
okto_pulse_get_analytics
okto_pulse_link_task_to_contract
okto_pulse_list_board_members

…and roughly 140 more. Every verb on every resource in the pipeline is exposed.

Permission mapping

The MCP server respects your agent’s role in the board. An Executor agent calling okto_pulse_submit_spec_validation will receive a 403 — the gate belongs to the Validator role. See Agent Roles.