Stacktree for AI agents.

What every integration shares

• Same twelve verbs. publish_html, update_site, get_site, set_password, set_expiry, set_email_gate, set_agentation, list_sites, delete_site, link_wallet, list_feedback, resolve_feedback.
• Same npm package. stacktree-mcp — single source of truth.
• Same auth model. Anonymous first publish (24 h), stacktree login for persistence, OAuth 2.1 + DCR for hosted clients.
• Same replace-in-place loop. update_site works identically across every agent.
• Same code you can run yourself. Stacktree is source-available — the whole stack (worker, MCP server, dashboard) deploys onto your own Cloudflare account, no lock-in. Self-host it.

How to pick the right install

• Claude Code, Codex, Cursor — pick the matching agent page above. Each has the one-line install.
• Claude.ai (web) — paste https://api.stacktr.ee/mcp as a custom connector.
• Slackbot — connect Stacktree in the Slack app's MCP settings, then ask Slackbot to publish in plain language. How it works.
• n8n workflows — install the n8n-nodes-stacktree community node and any workflow (or AI Agent node) gets publish, update, gates, and feedback as typed operations. How it works.
• Anything else MCP-compatible — use the package via npx -y stacktree-mcp over stdio, or hit the HTTP endpoint with OAuth.
• In-browser agents (WebMCP) — the dashboard registers its site actions on document.modelContext where the browser supports it, so an agent working alongside a signed-in human calls the same verbs without an API key. How and why.

Agents can pay for their own hosting

Most agents inherit an identity a human set up: the installer signs you in, or you drop in an API key. A fully autonomous agent has no human to do that. So Stacktree lets the agent pay for itself, with no person in the loop, two ways.

Pay per publish at the front-door. The simplest path: POST your HTML to agents.stacktr.ee/api/publish, get back a 402, pay $0.50, and the page publishes to a private link. No key, no account. It is multi-rail on one endpoint, so the agent pays with whatever it holds: x402 on Base or Solana, or MPP (the standard from Stripe and Tempo) on Tempo. Gas is covered, so the agent only signs.

Or buy a persistent key. For an agent that publishes repeatedly, /provision returns a 402; pay $1 over x402 or MPP and get a persistent stk_live_ key, then buy unlocks the same way. No wallet? One call to /pay/sessions returns a pay link plus a terminal QR, the human at the terminal pays by card in about two taps, and the agent continues mid-task.

Claim it later. The wallet that pays at the front-door is recorded with each page, so a human can claim those pages from the dashboard, or the agent can self-link them with the link_wallet MCP tool. Anonymous publishing stays free; paying is just how a headless agent earns durable, ownable hosting. We walked the whole loop, including the real on-chain payments, in An AI agent paid us $1 to provision itself and how agents pay us over MPP.