Labsco
MCP SERVER

Two tools and a JavaScript surface: reasoning that leaves an auditable ledger, and a hub where agents divide the work.

Reasoning Scaffolds & Agent Workflow Engines
Summary
Two tools that do not grow with the feature set.

Instead of registering a tool per operation, everything is reached by writing JavaScript against a catalog, so the context cost stays flat as the operation list grows. Worth knowing before you commit: the author says it is currently tuned for Claude Code, with other clients still being worked on.

What it is

An MCP server for structured, multi-agent reasoning. Every step is recorded as a numbered, timestamped thought linked to its predecessors and kept across sessions, with a browser UI for watching it happen live.

What you get
  • Exactly two MCP tools — `thoughtbox_search` to query the catalog with JavaScript, and `thoughtbox_execute` to chain operations through the `tb` SDK
  • Four reasoning patterns as first-class operations: forward from 1 to N, backward from the goal, branching into parallel explorations, and revision of an earlier thought
  • Thought types that record what kind of step it was — `reasoning`, `decision_frame`, `action_report`, `belief_snapshot`, `assumption_update`, `context_snapshot`, `progress`
  • 28 operations covering identity, workspace management, problems, proposals, consensus, channels and status reporting
  • Six agent profiles with their own mental models: `MANAGER`, `ARCHITECT`, `DEBUGGER`, `SECURITY`, `RESEARCHER`, `REVIEWER`
  • The Observatory at `http://localhost:1729` — a live graph over WebSocket, branches collapsed into clickable stubs, a detail panel per node, and switching between active sessions
  • A knowledge graph that survives sessions, with typed relations such as `BUILDS_ON`, `CONTRADICTS` and `SUPERSEDES` and visibility set to `public`, `agent-private` or `team-private`
  • Notebooks that mix documentation with executable JavaScript or TypeScript in an isolated environment
Requirements

Docker and Docker Compose — `docker compose up --build` brings up the server on port 1731 with the Observatory on 1729 and the observability stack behind them. Storage defaults to the filesystem under `~/.thoughtbox`; the `supabase` backend needs `SUPABASE_URL` and `SUPABASE_SERVICE_ROLE_KEY`. Local development needs Node.js 22+. MIT.

Setup effort

One command — docker compose up --build