Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.oktolabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

MCP setup

Pulse exposes 198 tools via the Model Context Protocol on :8101. Any MCP-compatible coding agent can connect to it. The agent then has full access to your board: creating ideations, writing specs, moving cards, querying the knowledge graph, and closing tasks with evidence.

How it works

okto-pulse init --agents writes .mcp.json in your project directory. Most MCP-compatible agents auto-detect this file when launched from the same directory.
{
  "mcpServers": {
    "okto-pulse": {
      "url": "http://localhost:8101/mcp?api_key=dash_..."
    }
  }
}
The api_key scopes the agent to your board and authenticates its tool calls. Treat it as a secret — do not commit .mcp.json to a public repository.

Per-agent setup

Claude Code auto-detects .mcp.json in the working directory.
  1. Run okto-pulse init --agents in your project root.
  2. Start Claude Code from the same directory.
  3. Confirm Pulse appears in the MCP server list: /mcp
That is the full setup. Claude Code re-reads .mcp.json on each session start.
  1. Run okto-pulse init --agents to generate .mcp.json.
  2. Open Cursor → PreferencesMCP.
  3. Paste the MCP URL from .mcp.json:
    http://localhost:8101/mcp?api_key=dash_...
    
  4. Save and restart Cursor.
Cursor also auto-detects .mcp.json in project roots in newer versions — check your Cursor release notes.
Cline auto-detects .mcp.json in the project directory.
  1. Run okto-pulse init --agents.
  2. Open the project in VS Code with the Cline extension active.
  3. Cline picks up the MCP server automatically.
Windsurf auto-detects .mcp.json in the project directory.
  1. Run okto-pulse init --agents.
  2. Open your project in Windsurf.
  3. The okto-pulse server appears in the Cascade tool list.
Codex supports user-wide MCP configuration via ~/.codex/config.toml.Add the following block:
[[mcp_servers]]
name = "okto-pulse"
url  = "http://localhost:8101/mcp?api_key=dash_..."
Replace the URL with the one from your generated .mcp.json. Restart any running Codex session to pick up the new server.
  1. Open Claude Desktop → Settings → Developer → MCP Servers.
  2. Add a new server entry:
{
  "okto-pulse": {
    "url": "http://localhost:8101/mcp?api_key=dash_..."
  }
}
  1. Restart Claude Desktop.

Verify the connection

Ask your agent to list available Pulse tools or inspect your board:
Use the Okto Pulse MCP tools. List the available boards and summarize
the current active work.
A correctly connected agent will enumerate boards and return a summary of ideations, specs, and open cards.

Regenerate .mcp.json

If you changed the MCP port, rotate the API key, or moved to a new project directory:
okto-pulse init --agents
To regenerate config for a specific agent only:
okto-pulse init --agents claude

Security

  • .mcp.json contains your agent API key. Add it to .gitignore.
  • The MCP URL with ?api_key= is equivalent to a password — do not paste it into issues, Slack, or docs.
  • The key scopes the agent to your local board only. It does not grant access to any remote service.

What the agent can do

Once connected, your agent has access to the full Pulse pipeline via MCP tools:
CategoryExamples
IdeationsCreate, advance, answer Q&A, evaluate scope
RefinementsInvestigate, cite evidence, add knowledge entries
SpecsWrite acceptance criteria, business rules, test scenarios, decisions
SprintsSuggest scope, create, evaluate
CardsCreate, move, attach evidence, close with conclusions
ValidationsSubmit spec and task validation with structured evidence
Knowledge GraphQuery decisions, detect contradictions, trace supersedence chains
The agent is expected to query the knowledge graph at the start of each ideation and refinement — prior decisions and constraints live there, not in the chat context.

Next steps

First workflow

Run your first ideation-to-cards session with a connected agent.
Last modified on May 8, 2026