Atisbo
io.github.brian8a1/atisboVersion 1.0.0MCP tools over one Atisbo workspace: Signals, Opportunities, Backlog, Decisions, Living Documents.
Status
Responds309 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:47 UTC
- Latency
- 309 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://app.atisbo.dev/api/mcpResponds309 msNo sign-in
Claude Code
claude mcp add --transport http atisbo https://app.atisbo.dev/api/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: atisbo
Remote MCP server URL: https://app.atisbo.dev/api/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"atisbo": {
"url": "https://app.atisbo.dev/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"atisbo","type":"http","url":"https://app.atisbo.dev/api/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
8 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
atisbo_analyzeBroad analytical query over claims, solutions, or activity: time filters, grouping, metrics, ready-to-render chart artifact. Use FIRST for analytical questions spanning entities or time windows; a single-entity drill-down is atisbo_lookup mode=get with the entity id. | No | Yes | Not declared | Not declared |
atisbo_captureCapture Signals or knowledge; update, patch or add evidence to artefacts. | Yes | No | Not declared | Not declared |
atisbo_connectWHERE Atisbo gets its signals. Modes: list, catalog, create (returns endpoint), configure, pause, resume, sync_now, delete (soft-disconnect). THE CATALOG IS NOT THE BOUNDARY: almost anything connects — call catalog and read `fallback` before saying "Atisbo cannot ingest that". Atisbo only READS a connected system. create returns the signing secret shown ONCE — relay to the human immediately. | Yes | No | Not declared | Not declared |
atisbo_decideCURATE: evidence review/grouping, deal-breakers. EXECUTE: create, update, dispatch or delete Solutions, record Outcomes. DOCUMENT/GOVERN: living docs, coverage, schedules, knowledge, strategy. log_decision is only for external decisions; mutations log themselves. Writes require UUIDs. mode=declare_pm_exception marks a CLAIM as needing a human decision. | Yes | No | Not declared | Not declared |
atisbo_lookupFind or open Atisbo entities: snippets, queues, outcomes and implementation context across modes. | No | Yes | Not declared | Not declared |
atisbo_mapCreate/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup (merge/split), build_macros (macros, preview first). Prefer mode=apply for MECE grouping. Anchor and link_claims put a claim on a node differently and both refuse the wrong map kind: anchor sets the TAXONOMY category (auto_node_id); link_claims adds STRUCTURAL-map membership. | Yes | No | Not declared | Not declared |
atisbo_orientWorkspace orientation. Modes: snapshot, whats_new, strategy, integrations. Continue the user's existing workflow; never create a parallel backlog. Living docs cite snippet:// refs — open atisbo_lookup mode=open; corpus via claim depth=work; aggregates via atisbo_analyze; edit via atisbo_lookup mode=doc_patch_context then atisbo_capture mode=patch_artefact. | No | Yes | Not declared | Not declared |
atisbo_supportDiagnose Atisbo, including "I connected a source and nothing appeared", "I sent text and no opportunity formed", or "my data is missing". Checks integrations, ingestion, clustering, gates, key scope and migrations, then returns a playbook. share_report files only diagnostics + your text. Use atisbo_lookup/atisbo_analyze for backlog. | No | Yes | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Repository
- Not given
- Categories (suggested)
- Project managementDocumentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared