Connect-MCP

Atisbo

io.github.brian8a1/atisbo · v1.0.0

MCP tools over one Atisbo workspace: Signals, Opportunities, Backlog, Decisions, Living Documents.

MCPremoteAPI keyAnalytics & marketing

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 8 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 83/100

What it does: 8 tools · 4 read, 4 write (incl. delete/pay) · Documents & PDF, Analytics & marketing

Test call atisbo_orient: needs a key: rpc error: Invalid or missing API key (1,227 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +5
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://app.atisbo.dev/api/mcp

Tools

8 tools listed at last check
  • atisbo_orient Workspace orientation. Modes: snapshot, whats_new, strategy, integrations. Continue the user's existing workflow; never create a parallel backlog. Living docs cite snippet:// refs — open with atisbo_lookup mode=open, full corpus via claim depth=work, aggregates via atisbo_analyze. Edit via atisbo_lo
  • atisbo_lookup Find or open Atisbo entities: snippets, queues, outcomes and implementation context across modes.
  • atisbo_capture Capture Signals or knowledge; update, patch or add evidence to artefacts.
  • atisbo_decide PM decision facade. CURATE: 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 U
  • atisbo_map Map facade: create/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup (merge/split). Prefer mode=apply for full MECE categorization. TWO WAYS TO PUT A CLAIM ON A NODE, not interchangeable: mode=anchor sets the TAXONOMY category (auto_nod
  • 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 THE BOUNDARY: almost anything connects (push app, daily-pull app, raw webhook/email) — call catalog and read `fallback` before ever saying
  • atisbo_analyze Broad 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.
  • 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, ingestion, clustering, gates and key scope, then returns a playbook. share_report files only diagnostics + your text. Use atisbo_lookup/atisb

Badge

Connect-MCP badge for io.github.brian8a1/atisbo

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.brian8a1/atisbo.svg)](https://clawy.uk/mcp/s/io.github.brian8a1/atisbo)

Website