MCP Server

Atisbo exposes a Model Context Protocol (MCP) server that lets agents work with the same Signals, Opportunities, Backlog, Groups, Decisions, Living Documents, and Outcomes shown in the app.

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants call external tools. When Claude or another AI has your Atisbo MCP configured, it can:

• Review Signals and evidence provenance
• Search Opportunities about a specific topic
• Read your Strategy Stack and roadmap
• Prepare portfolio-level Product Reviews
• Create or update Solutions after a human Decision
• Brief a designer or engineer on one Backlog item and its Living Document
• Connect a design or PR handoff to In Review
• Record the observed Outcome of a Done Solution

Agent Skills add interaction guidance on top of these tools. They do not add a separate Atisbo planning or implementation pipeline.

Setup

The short way

Go to Settings → Account → Connect agents, pick your agent, and click Generate setup command. You get one block to paste into your terminal — it connects this workspace and installs the Atisbo skills in the same step. Most people should stop here.

The manual way

If you are wiring a client yourself, generate the connection from the same screen and use the key it gives you. The key is shown once.

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "senso": {
      "type": "http",
      "url": "https://app.atisbo.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

Custom Agent (JSON-RPC 2.0)

Start with the compact tools returned by tools/list. A normal workflow should begin with senso_orient, then call a more specific tool only when the answer needs it.

curl -X POST https://app.atisbo.dev/api/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <your-api-key>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "senso_orient",
      "arguments": { "mode": "snapshot" }
    }
  }'

Available Tools

tools/list returns eight intent-level tools by default. Each one takes a mode, so the surface stays small while the capability does not.

Tool	Description
senso_orient	Workspace orientation: snapshot, what changed, strategy, or connections
senso_lookup	Read claims, solutions, maps, nodes, context, or living docs
senso_capture	Ingest a signal, save knowledge, or attach evidence
senso_decide	Triage, create/update Solutions, set priority boosts, record outcomes, or log decisions
senso_map	Read or edit the product taxonomy map
senso_connect	Find and create data sources — see Connect with your agent
senso_analyze	Run broader product analysis over claims, solutions, or activity
senso_support	Diagnose why the workspace is not behaving as expected

A larger surface of single-purpose primitives also exists, requested with ?surface=full. It changes discovery only — every primitive is callable through tools/call at any time, whether or not tools/list advertised it. Most clients should not ask for it: eight tools cost an agent far less context than eighty.

Tool Reference

senso_orient

Returns a compact workspace overview.

Input:

{
  "mode": "snapshot"
}

Output:

{
  "data": {
    "top_claims": [],
    "solutions": [],
    "recommended_next_tools": []
  },
  "meta": {
    "timestamp": "2026-03-07T14:30:00Z"
  }
}

senso_lookup

Reads a specific object or searches by name/reference. Use this after senso_orient when you need detail.

Input:

{
  "mode": "claim",
  "id": "claim-uuid",
  "depth": "summary"
}

senso_decide

Applies product decisions. Resolve names to UUIDs before mutating.

Input:

{
  "mode": "update_solution",
  "solution_id": "solution-uuid",
  "priority_boost": 1.5,
  "comment": "Prioritized for the current strategic commitment."
}

The current Board order uses manual rank first, then evidence-weighted priority multiplied by the PM's explicit boost. RICE fields are retained only for legacy audit/effort workflows and do not rank Solutions.

Authentication

All MCP requests require a Bearer token in the Authorization header. Keys are:

• Scoped to one tenant and one workspace
• Created and revoked in Settings → Account → Connect agents
• Hashed before storage (SHA-256) — Atisbo never stores the plaintext key, so a lost key is replaced rather than recovered

Usage Protection

Atisbo tracks MCP usage as work units so the platform can detect runaway agent loops without treating every request as equal. Simple reads are cheap; write tools, external tools, long-running tools, and batches count for more.

Normal clients should use the compact surface and avoid repeated tools/list calls. Hard rate limiting is reserved for incident-response protection, not as the default user experience.

Protocol

Atisbo's MCP server implements JSON-RPC 2.0 over HTTPS:

• Endpoint: POST https://app.atisbo.dev/api/mcp
• Protocol version: 2024-11-05
• Idempotency: Write operations accept X-Idempotency-Key header
• Retries: Query tools have automatic retry with circuit breaker

See the MCP specification for full protocol details.