Agent Tree vs Laminar API + MCP

Agent Tree 50

Framework reading, docs a model can follow, as superpowers was read. types/index.d.ts types the pane's state, and plugin.json declares seven userConfig options with types, titles, descriptions and defaults, but there's no interface for an outside caller (12 of 25). README in English and German, a nine-step GUIDE.md and PRIVACY.md, all Markdown in the repository; no llms.txt (10). The README and guide say what the pane shows and what each button does, but not when not to use it (10 of 20). Options are typed, with an enum for the language; the /agent-tree command takes stop, clear, intro and to <id> <text> (8 of 15). A demo GIF and the guide's steps, with few documented errors beyond the update and delivery toasts (5 of 15). Semver tags but no changelog or release notes read (5 of 15). 50 in all.

Laminar API + MCP 88

OpenAPI in the docs, and the MCP tools take typed schemas generated from Rust structs (25). llms.txt and Markdown docs (10). The tool descriptions are among the best in the category. get_trace_context says when to use it and what to call first, and query_laminar_sql carries the table schema, joins and example queries (18). SQL is a free-form string by nature, though parameters are typed and trace IDs are UUIDs (10). The SQL API documents its 400, 401 and 429 bodies with examples (13). Monthly changelog without dates per entry, and a /v1 API (12).

Agent Tree 60

Self-hosted rule. No payment protocol (0). Free under MIT with nothing to buy (20). No card or account (20). A person installs it with one command and no sign-up (20). 60 in all.

Laminar API + MCP 30

No x402 (0). Per-GB prices and Signals token prices published without login (20). The Free plan exists with 1 GB and 7 days, but the pricing page doesn't say whether a card is needed, so half (10). A person signs up in a browser to create a project key (0).

Agent Tree 60

v0.5.4 tagged on 29 October 2026 and a commit on 31 October (30). 19 tags from v0.2.2 (24 October) to v0.5.4 (29 October), far more than three in 90 days (20). Issue and pull-request replies couldn't be read, as github.com was unreachable (5 of 25). Not in Claude's official plugin directory; claude.com/plugins/agent-tree answered 404 (0). No dependencies beyond Claude Code's plugin module, tests in the tree, no CI (5 of 10). 60 in all.

Laminar API + MCP 83

TypeScript SDK 0.8.49 on 2026-09-23, Python SDK 0.7.64 on 2026-09-21 and server v0.2.5 on 2026-09-13, with commits on the dev branch on 1 October (30). Five server tags and well over three SDK releases since 3 July (20). We couldn't load issue reply times (10). Both SDKs current (15). Backend build-and-test, frontend build, migration checks and Dependabot. Pass state not checked (8).

Agent Tree 33

Local-package reading, as for superpowers and tokeneconomizer. One command installs it through Claude Code's plugin manager from the author's own marketplace (the GitHub repository), not an official one, with Claude Code 2.1.292 or later stated and 2.1.316 tested (15 of 20). No .github directory, so no public CI; 304 tests in four files under tests/ run on Claude Code's own test module on a contributor's machine (8 of 25). Issues couldn't be read, as github.com was unreachable from this session (5 of 25, unchecked). 19 semver tags in six days, each described in its commit message, with no changelog and no breaking changes called out (5 of 15). Version 0.5.4 (0). 33 in all.

Laminar API + MCP 50

Better Stack page at status.laminar.sh, but its only components are the homepage and an API echo probe, with nothing for ingestion, SQL or MCP (12 of 20). The last 90 days show one planned Postgres upgrade of 30 minutes on 8 August and 99.943 per cent on the echo probe (20, minor only). The docs say queries are rate limited per project but give no numbers (0). The SQL API documents 429 with an instruction to retry with backoff. Nothing for ingestion (8). No SLA found on the pricing page or in the docs (0). API, SQL and MCP are GA (10).

Agent Tree 67

Framework reading, how much a coding agent has to carry. The plugin adds no tools, skills or prompt text to the model's context. Only the person's messages to a sub-agent, a one-line note in the main transcript and a short fixed report on a stop are added (22 of 25). Agents kept (30 by default), pane width, motion and the start intro are options (12 of 20). Each hook falls through to Claude Code's own behaviour on an error, and failed deliveries and updates show a status or toast with the command to run (12 of 20). Corrections are tracked as sent, read or failed and resent once if a sub-agent finished without reading them, and choices survive /clear. A stop can't be undone (13 of 20). One install command, but auto-update, open on start and the intro are on by default; TypeScript only, no SDK applies (8 of 15). 67 in all.

Laminar API + MCP 80

Three MCP tools, but the SQL tool's description embeds the whole table schema, so the list costs more context than the count suggests (18). Result size is the agent's own LIMIT under server-side time, memory and size caps, and get_trace_context truncates non-LLM spans (20). Tool failures come back with isError and a message. HTTP errors are a single error field (17). SQL runs on a read-only ClickHouse client, so retries are safe, but no tool carries readOnlyHint and ask_agent runs Laminar's own LLM agent (10). One required argument per tool. Python and TypeScript SDKs and a CLI (15).