io.github.brian8a1/atisbo
name:io.github.brian8a1/atisbo
MCP tools over one Atisbo workspace: Signals, Opportunities, Backlog, Decisions, Living Documents.
- transport:
- remote
- credential class:
- self-provisionable
Owner verification
Not yet verified. Verifying proves you control this server and is free, permanently — it never changes a published score.
Start verification →Tools
- atisbo_analyzeshallow
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; for single-entity drill-downs atisbo_lookup mode=claim or atisbo_lookup mode=node is enough.
- atisbo_captureshallow
Compact facade for bringing knowledge into Atisbo. Modes: signal, knowledge, update_artefact (FULL REPLACE of a living doc), patch_artefact (validated section-level patches — preferred; get content_hash via atisbo_lookup mode=doc_patch_context first), add_artefact_evidence. For feedback, transcripts, notes, docs, and evidence blocks.
- atisbo_connectshallow
Compact facade for WHERE Atisbo gets its signals — it CONNECTS sources, not just describes them. Modes: list (connections + live status), catalog (ingestible sources; query filters), create (returns the endpoint), configure, pause, resume, sync_now (pull sources only). Call list before any mutation. THE CATALOG IS NOT THE BOUNDARY: almost anything connects — push app (composio_catalog), daily-pull app (composio_actions, ~1,000 apps), raw webhook/email. Never answer "Atisbo cannot ingest that" from an empty search; call catalog and read `fallback`. Atisbo only READS a connected system, never writes. create returns an endpoint + signing secret shown EXACTLY ONCE — relay both to the human immediately.
- atisbo_decideshallow
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 UUIDs. mode=declare_pm_exception marks a CLAIM as needing a human decision (SEN-180).
- atisbo_lookupshallow
Find or open Atisbo entities. work_queue returns an external agent action_queue, completion, Monitoring and pm_exceptions. outcome_review exposes post-launch evidence; implementation_context loads product intent. Mutate with atisbo_decide or atisbo_map.
- atisbo_mapshallow
Compact facade for map work: create/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup claims (merge/split — mode=regroup). Prefer mode=apply for full MECE categorization. TWO WAYS TO PUT A CLAIM ON A NODE, not interchangeable: mode=anchor sets the TAXONOMY category (claims.auto_node_id — one per claim, what the Board groups by), refusing non-taxonomy maps; mode=link_claims adds membership in a STRUCTURAL map (KPI tree, opportunity tree) while the claim keeps its category, refusing taxonomy maps.
- atisbo_orientshallow
Compact facade for workspace orientation. Modes: snapshot (task-optimized overview), whats_new (delta digest), strategy (Strategy Stack), integrations (source health). Atisbo is one ordered list of what to do next. AGENT CONTRACT: continue planning/design/implementation/review already in progress in the user's own tools — never a parallel Atisbo workflow or local backlog. EVIDENCE DEPTH: Living Documents cite evidence as snippet:// refs — open only the cited Signals via atisbo_lookup mode=open; atisbo_lookup mode=claim depth=work only for the full corpus, atisbo_analyze for aggregates. Living-doc editing: atisbo_lookup mode=doc_patch_context then atisbo_capture mode=patch_artefact.
- atisbo_supportshallow
Report an Atisbo problem and get a real answer in the same call. Also when nothing errored but the workspace misbehaves: "I connected a source and nothing appeared", "I sent text and no opportunity formed", "my data is missing". Diagnoses YOUR workspace (integration freshness, ingestion backlog, clustering queue, quality-gate rejections, plan gates, key scope), then answers from support playbooks — most causes are recoverable config in your account. If nothing is wrong on your side, a verdict-only report may be filed: ONLY diagnostic results plus your text, never feedback content, customer names or document bodies. For backlog questions use atisbo_lookup or atisbo_analyze.
Embed this server’s score
Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.
[](https://vouch.tools/servers/d6ce9278-1fe9-44a5-80a9-f302e789ec7d)