# Brian8a1 Atisbo MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.brian8a1%2Fatisbo
Registry id: `mcp-registry/io.github.brian8a1/atisbo`
Status: live (checked 2026-10-26T20:15:38.842Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4944
- Outages (90 days): 3

## Install

```json
{
  "mcpServers": {
    "brian8a1-atisbo-mcp-server": {
      "type": "http",
      "url": "https://app.atisbo.dev/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http brian8a1-atisbo-mcp-server https://app.atisbo.dev/api/mcp
```

## Tools (8)

- `atisbo_analyze`: Broad analytical query over claims, solutions, or activity: time filters, grouping, metrics, ready-to-render chart artifact. Use FIRST for analytical questions 
- `atisbo_capture`: Capture Signals or knowledge; update, patch or add evidence to artefacts.
- `atisbo_connect`: WHERE Atisbo gets its signals. Modes: list, catalog, create (returns endpoint), configure, pause, resume, sync_now, delete (soft-disconnect). THE CATALOG IS NOT
- `atisbo_decide`: CURATE: evidence review/grouping, deal-breakers. EXECUTE: create, update, dispatch or delete Solutions, record Outcomes. DOCUMENT/GOVERN: living docs, coverage,
- `atisbo_lookup`: Find or open Atisbo entities: snippets, queues, outcomes and implementation context across modes.
- `atisbo_map`: Create/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup (merge/split), build_macros (macros, pr
- `atisbo_orient`: Workspace orientation. Modes: snapshot, whats_new, strategy, integrations. Continue the user's existing workflow; never create a parallel backlog. Living docs c
- `atisbo_support`: Diagnose Atisbo, including "I connected a source and nothing appeared", "I sent text and no opportunity formed", or "my data is missing". Checks integrations, i

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.