OpenApps

AgentStack MCP server — tools & history

AgentStack MCP server: observed open status, tool schemas, linked apps and version history.

AgentStack

Endpoint: https://agentstack.tech/mcp

Observed status: open. Checked: 2026-10-12T05:06:02+00:00.

Linked apps

  • AgentStack

    One MCP tool for the live AgentStack catalog — hosting (/s/), storage, 8DNA, auth, logic, payments, agents, RAG, messenger, integrations.

  • AgentStack (agentstack.tech)

    Backend platform for AI agents: one agentstack.execute tool runs batched steps over ~668 actions (hosting, storage, auth, payments, CRM, app builder). OAuth 2.1 or X-API-Key.

Observed tools

  • agentstack.execute — AgentStack MCP = Work Graph control plane. After session + context.project_id: agents.work_next (mcp_work_loop_v1) -> plan_claim -> plan_execute (CAS/leases). Follow packet.next_action; catalog/discovery.search only if no packet. One-shot CRM/upload may call domain actions directly. Spine: agents.plan_get -> agents.work_next -> agents.plan_claim -> agents.plan_execute. Cheap and batchable on one sync execute: agents.work_next, agents.plan_get, agents.plan_claim. One per sync execute: agents.plan_propose, agents.plan_apply_proposal, agents.plan_recovery_scan, context.get. Anti-pattern: Do not pick tools from catalog when packet.next_action is present. Mandatory session order: authenticate -> session probe auth.get_profile (alias auth.me) -> select/create project -> set context.project_id on every batch -> Work Graph loop. Playbook GET /mcp/prompts/get?name=agentstack_session_setup (recipe mcp_session_setup). Packs session.v1 and batch.v1: GET /mcp/actions field execute_budget.packs. Send context.project_id; other session fields default server-side. Sync POST /mcp is lane mcp_batch (60000 ms) for the whole batch - not an RBAC cap. One expensive step per sync execute (bots.simulate and other heavy actions per execute_budget; agents.run with wait=true; agents.plan_apply_proposal, agents.plan_propose, agents.plan_recovery_scan, context.get). agents.work_next, agents.plan_get, and agents.plan_claim are cheap and may share that batch. LLM-heavy steps widen to ai_stream (180000 ms). Large suites: options.async=true then poll discovery.job_status (REST GET /mcp/jobs/{job_id}). Cite catalog_actions_public from GET /mcp/actions/summary. There is one execute tool (agentstack.execute); do not quote tools_count as 'N tools'. Do not invent rules.* or webhooks.* (prefer logic.* and integrations.*).

Data as of 2026-10-12T05:06:02+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections