About AgentStack (agentstack.tech)
AgentStack is a backend for agents that coordinates work through a queued Work Graph rather than requiring agents to browse a large action catalog. Its MCP interface batches access behind one tool and guides each turn through a next action and a verify-before-publish cycle.
Key features
- 01Single batched MCP tool: agentstack.execute
- 02Work Graph provides the next action
- 03Claim and execute queued work
- 04Sandbox, review, and promote changes
- 05Publish after project-defined checks
Use cases
- 01Coordinate agents across queued tasks
- 02Reduce catalog browsing during an agent loop
- 03Make live data changes through review and promotion
MCP support
The server exposes one batched tool, `agentstack.execute`. The Work Graph supplies the next action, while agents claim and execute work through the MCP loop.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://agentstack.tech/mcpclaude mcp add --transport http agentstacktech-agentstack https://agentstack.tech/mcp{"mcpServers":{"agentstacktech-agentstack":{"type":"http","url":"https://agentstack.tech/mcp"}}}Open in Cursor{"servers":{"agentstacktech-agentstack":{"type":"http","url":"https://agentstack.tech/mcp"}}}Open in VS Code{"mcpServers":{"agentstacktech-agentstack":{"type":"http","url":"https://agentstack.tech/mcp"}}}{"mcpServers":{"agentstacktech-agentstack":{"serverUrl":"https://agentstack.tech/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
1| Parameter | Type | Required | Description |
|---|---|---|---|
| steps | array | Yes | Steps; one heavy LLM per sync execute. |
| context | object | No | session.v1; project_id required. |
| context.project_id | integer | No | Tenant project id. |
| options | object | No | batch.v1 controls. |
| options.goal | string | No | Goal text for playbook. |
| options.async | boolean | No | Queue; poll discovery.job_status. |
| options.envelope | enum | No | compact (default) | full — ADR MCP_EXECUTE_ENVELOPE_COMPACT_V2compact | full |
| options.recipe_id | string | No | MCP recipe id. |
| options.stopOnError | boolean | No | Stop on first failure. |
| options.continueOnError | boolean | No | Continue after failure. |
| options.idempotency_key | string | No | Retry receipt key. |
Details
From the project READMEAgentStack
After one bind, the agent does not shop the catalog. Work Graph hands it the next step. Live edits stay on the safe circle: write a copy, pass the checks, then publish.
One MCP tool, agentstack.execute. The server holds the plan. Each turn is one action. Idle is a valid answer. Blocked names the unblock.
Story: agentstack.tech/work-graph · Contract: docs/plugins/WORK_GRAPH.md · Safe circle: agentstack.tech/mcp-docs#safe-cycle
The loop
session → context.project_id → agents.work_next → packet.next_action → claim / execute → work_next
Recipe mcp_work_loop_v1. Prompt agentstack_closed_loop_autonomy.
flowchart LR
S[Session] --> B[Bind project]
B --> W[work_next]
W --> N[next_action]
N --> X[Claim and execute]
X --> W
When that step changes live data, the same project runs the safe circle:
connect → sandbox → review → promote
The agent writes a generation. Customers stay on the previous copy until the checks pass. The project’s own rule publishes it: at once, or in stages.
| Who | Without the loop | With Work Graph |
|---|---|---|
| Founder with open loops | Every new chat re-reads the tool menu | The outcome is written once. The next chat takes the head of the queue |
| A person with more tasks than hours | The agent invents a tool and spends the window choosing | The list says ready, blocked, or idle |
| A business that needs the work finished | Thrash between catalog, guess, and retry | Claim, execute, verify, on the same project as the site and the payments |
| Someone wiring an agent | Paste the catalog into the prompt | agents.work_next, then packet.next_action |
Measured on 2026-10-07
Local registry build. Not a production traffic sample. Not a provider tokenizer. Bytes ÷ 4 is an English size estimate.
| Payload | UTF-8 bytes | Rough tokens |
|---|---|---|
Example next_action plus two alternatives | 250 | ~63 |
discovery.search, first 20 compact rows | 8,889 | ~2,222 |
| Handshake contract JSON, once | 11,297 | ~2,824 |
| Compact search, 50 rows (HTTP max) | 20,852 | ~5,213 |
| Full registry catalog JSON (795 actions in that build) | 1,680,071 | ~420,018 |
The full catalog is 6,720× that example packet. A 20-row search page is 35.6× it. The public catalog you should quote is 714 actions — live GET /mcp/actions/summary. Do not add the byte ratio and the operator targets into one savings claim.
| Signal | Target |
|---|---|
Autonomous loops that follow packet.next_action | ≥ 90% |
| Catalog shopping while a packet is already present | ≤ 5% |
Those are steady-production goals, not a live counter. Method and scenarios: docs/plugins/WORK_GRAPH.md.
Docs
This repository is the public documentation (English, user- and integrator-facing): web product, MCP, plugins, REST, RAG, sandboxes, and examples.
If you use the website: docs/USER_FEATURES_GUIDE.md.
If you build a product: docs/BUILD_YOUR_PRODUCT.md — @agentstack/sdk, optional genetic-ai-starter.
If you run agents on a large codebase: docs/genetic-system/.
If you integrate: docs/MCP_AND_ECOSYSTEM.md — start with the loop, then the catalog (714 actions · docs/MCP_SCALE.md).
REST / OpenAPI: docs/OPENAPI.md — Swagger · openapi.json.
npm SDK: @agentstack/sdk · docs/sdk/
Full index: docs/README.md · What's new: docs/WHATS_NEW.md
Open source kit
| Repo | Branch | Notes |
|---|---|---|
| genetic-ai-starter | main | Map-first install: npx @agentstack/genetic-ai-starter init. SoT lives in this repo under genetic-ai-starter/ when you have the monorepo. |
Plugins
| Plugin | Notes |
|---|---|
| cursor-plugin | v0.4.18, gen3 — rules, skills, commands, agents, hooks; Plugin MCP Connect and OAuth 2.1 device code |
| claude-plugin | Claude Desktop / API installers |
| gpt-plugin | ChatGPT / OpenAI ecosystem |
| vscode-plugin | VS Code marketplace distribution |
Product
- Site: agentstack.tech
- Work Graph: agentstack.tech/work-graph
- GitHub org: github.com/agentstacktech
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.