Index / MCP servers / Atisbo

Atisbo MCP server

Atisbo is an MCP server with 8 tools an agent can call, among them atisbo_analyze, atisbo_capture, atisbo_connect. It answers at https://app.atisbo.dev/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 21 October 2026, succeeded.

Status
Answering
Tools
8
Reliability
6 of 6 checks
Response time
467 ms
Transport
streamable HTTP
Last checked
21 October 2026

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

Description as the publisher wrote it.

The 8 tools Atisbo offers

ToolWhat it does
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; for single-entity drill-downs atisbo_lookup m
Inputs: subject, mode, domain, time_range, filters, group_by
atisbo_captureCapture Signals or knowledge; update, patch or add evidence to artefacts.
Inputs: mode, text, items, title, content, change_summary
atisbo_connectCompact 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,
Inputs: mode, connection_id, query, recipe_id, kind, label
atisbo_decidePM 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 ex
atisbo_lookupFind or open Atisbo entities. Modes expose snippet text + attachment URLs, queues, outcomes and implementation context.
Inputs: mode, ref, refs, query, types, target_id
atisbo_mapCompact 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 W
Inputs: mode, claim_ids, note, name, description, map_id
atisbo_orientWorkspace orientation. Modes: snapshot (overview), whats_new (delta), strategy, integrations. Continue the user's existing workflow; never create a parallel backlog. Living docs cite snippet:// refs: open cited Signals with atisbo_lookup mo
Inputs: mode, task, depth, limit, cursor, since_checkpoint
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 and key scope, then returns a playbook. share_report
Inputs: problem, area, observed_error, share_report

Add Atisbo to your AI client

Every block below points at https://app.atisbo.dev/api/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http atisbo https://app.atisbo.dev/api/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "atisbo": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.atisbo.dev/api/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "atisbo": {
      "url": "https://app.atisbo.dev/api/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "atisbo": {
      "type": "http",
      "url": "https://app.atisbo.dev/api/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "atisbo": {
      "url": "https://app.atisbo.dev/api/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "atisbo": {
      "serverUrl": "https://app.atisbo.dev/api/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "atisbo": {
      "url": "https://app.atisbo.dev/api/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Atisbo
version: 0.0.1
schema: v1
mcpServers:
  - name: Atisbo
    type: streamable-http
    url: https://app.atisbo.dev/api/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "atisbo": {
      "httpUrl": "https://app.atisbo.dev/api/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "atisbo": {
      "type": "http",
      "url": "https://app.atisbo.dev/api/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "atisbo": {
      "url": "https://app.atisbo.dev/api/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fapp.atisbo.dev%2Fapi%2Fmcp&type=streamable_http&id=atisbo&name=Atisbo

Is Atisbo up right now?

It answered our last check on 21 October 2026 in 467 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Atisbo

Questions about Atisbo

How many tools does Atisbo have?

8, as returned by the server's own tools/list on 13 September 2026: atisbo_analyze, atisbo_capture, atisbo_connect, atisbo_decide, atisbo_lookup, atisbo_map, atisbo_orient, atisbo_support.

Is Atisbo down?

It answered our last check on 21 October 2026 in 467 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Atisbo to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://app.atisbo.dev/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Atisbo need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.brian8a1. Endpoint host: app.atisbo.dev. ARD identifier: urn:air:io.github.brian8a1:mcp:atisbo. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.