AgentStack

Descripción

AgentStack is a hosted backend platform that an MCP-capable assistant can operate. Through one tool, agentstack.execute, it runs batched steps against projects covering data, auth, CRM, automation, knowledge, hosting, payments and scheduled tasks. Actions are found with discovery search and checked with a preflight step before writes.

It runs as a remote streamable HTTP endpoint at https://agentstack.tech/mcp. Work on your projects needs an AgentStack API key from Profile → API Keys, sent in the X-API-Key header (Authorization: Bearer with the same key also works). In Cursor, AgentStack's plugin can sign in with OAuth instead. To try it without an account, ask the assistant to create a project: AgentStack makes an anonymous one, limited to one project and 1,000 Logic Engine calls a month, and returns an API key to add to your client's headers. Each batch needs a project ID in its context. The server also ships prompts for logic rules, scheduled tasks, project setup and session setup.

Qué puedes hacer

• Run batched AgentStack actions with one execute tool
• Discover available actions by describing a goal
• Run preflight checks before write operations
• Bind work to a specific project and manage its members
• Create backend logic rules and scheduled tasks
• Use built-in prompts for project and session setup

Herramientas 1

• agentstack.executePuede borrar

  Run AgentStack operations as steps with action and params, within a project context; can write or…

Leídas del servidor en funcionamiento el 7 oct 2026. Solo lectura, Escritura y Puede borrar son indicaciones que declara el servidor; tu cliente decide si te pregunta antes de ejecutar una herramienta.

Prompts de ejemplo

• Create a new AgentStack project for my online course shop.

• Search AgentStack for actions that manage customers and list them.

• Add a scheduled task that runs a logic rule every morning.

• Add a teammate to my project as a read-only member.

Configuración

Todos los clientes se conectan a agentstack.tech. Elige el tuyo; la página recuerda tu elección.

claude mcp add --transport http agentstack https://agentstack.tech/mcp --header "X-API-Key: <YOUR_API_KEY>"

{
  "mcpServers": {
    "agentstack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://agentstack.tech/mcp",
        "--header",
        "X-API-Key: <YOUR_API_KEY>"
      ]
    }
  }
}

{
  "mcpServers": {
    "agentstack": {
      "url": "https://agentstack.tech/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "agentstack": {
      "type": "http",
      "url": "https://agentstack.tech/mcp",
      "headers": {
        "X-API-Key": "${input:x-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "x-api-key",
      "description": "X-API-Key",
      "password": true
    }
  ]
}

{
  "mcpServers": {
    "agentstack": {
      "serverUrl": "https://agentstack.tech/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

codex mcp add agentstack --url https://agentstack.tech/mcp

[mcp_servers.agentstack]
url = "https://agentstack.tech/mcp"
env_http_headers = { "X-API-Key" = "X_API_KEY" }

gemini mcp add --transport http --header "X-API-Key: <YOUR_API_KEY>" agentstack https://agentstack.tech/mcp

{
  "mcpServers": {
    "agentstack": {
      "type": "http",
      "url": "https://agentstack.tech/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Insertar

Muestra AgentStack en un README o en tu web. Cada inserción enlaza a esta página, usa la URL propia del servidor y no instala cookies. Cómo funcionan las inserciones

La tarjeta, el iframe y el JSON están en inglés. Añade ?lang=it, fr, de o es a su dirección para otro idioma.

Insignia para README Tarjeta para web iframe JSON Prompt para la IA

Insignia para README

Markdown

[![AgentStack on mcp.tc](https://mcp.tc/i/agentstack/badge.svg)](https://mcp.tc/i/agentstack)

HTML

<a href="https://mcp.tc/i/agentstack"><img src="https://mcp.tc/i/agentstack/badge.svg" alt="AgentStack on mcp.tc" height="20"></a>

Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.

Tarjeta para web

HTML

<script src="https://mcp.tc/w/agentstack.js" async></script>

La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala cookies.

iframe

HTML

<iframe src="https://mcp.tc/embed/agentstack" title="AgentStack on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.

JSON

La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).

https://mcp.tc/i/agentstack.json

Qué significa cada campo

Prompt para la IA

Pégalo en un asistente de programación con IA, como Claude Code o Cursor, y añadirá la tarjeta de AgentStack a tu web.

Markdown

Añade a mi web la tarjeta de mcp.tc de AgentStack, un servidor MCP. Es un solo script estático: sin paso de build, sin paquetes que instalar, sin cookies.

Pon esta etiqueta donde deba aparecer la tarjeta. La tarjeta se muestra justo antes de ella:

```html
<script src="https://mcp.tc/w/agentstack.js" async></script>
```

Para mostrarla en otro sitio, pon allí este marcador y carga el mismo script una sola vez, por ejemplo antes de `</body>`. Deja el enlace dentro: lo ven los visitantes sin JavaScript.

```html
<div data-mcptc="agentstack"><a href="https://mcp.tc/i/agentstack">AgentStack on mcp.tc</a></div>
```

Opciones:
- `data-theme="light"` o `"dark"` en la etiqueta o el marcador fija los colores. Sin él, la tarjeta sigue el modo claro u oscuro del visitante.
- `data-size="compact"` da una tarjeta más pequeña, sin el eslogan.
- La variable CSS `--mcptc-max-width` en el marcador o en un elemento padre fija el ancho (por defecto `520px`).
- `?lang=` en la URL del script fija el idioma de la tarjeta: `en`, `it`, `fr`, `de` o `es`.

Si el sitio tiene una Content Security Policy, permite `script-src https://mcp.tc` e `img-src data:` (el icono va incrustado).

Para un README u otra documentación en Markdown, usa la insignia:

```markdown
[![AgentStack on mcp.tc](https://mcp.tc/i/agentstack/badge.svg)](https://mcp.tc/i/agentstack)
```

Referencia: https://mcp.tc/es/embed

Historial de cambios

Leemos la lista de herramientas de este servidor cada 3 horas y registramos lo que cambia. Última lectura: 8 oct 2026, 07:29 UTC.

1. 7 oct 2026, 22:33 UTC, Comprobación automática

   1 herramienta cambiada.

   Detalles, 7 oct 2026, 22:33 UTC

   Cambiadas 1

   • agentstack.executeesquema de entrada y esquema de salida
     • Descripción de context
       Antes

       ninguno

       Después

       Execute scope. Set project_id on every batch after the session probe.

     • Descripción de options
       Antes

       ninguno

       Después

       Batch controls: async jobs, recipes, playbook progress, and error policy.

2. 7 oct 2026, 16:36 UTC, Comprobación automática

   1 herramienta cambiada.

   Detalles, 7 oct 2026, 16:36 UTC

   Cambiadas 1

   • agentstack.executedescripción
     Antes

     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. 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). Sync POST /mcp is lane mcp_batch (60000 ms) for the whole batch - not an RBAC cap. One heavy LLM step per sync execute (bots.simulate, knowledge.playground, agents.run with wait=true); that step widens to ai_stream (180000 ms). Large suites: options.async=true then poll discovery.job…

     Después

     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. 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). 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, knowledge.playground, agents.run with wait=true, agents.plan_*, context.get); LLM-heavy steps widen to ai_stream (180000 ms). Large suites: options.a…

3. 7 oct 2026, 01:33 UTC, Comprobación automática

   1 herramienta cambiada. Instrucciones del servidor cambiadas.

   Nuevas instrucciones del servidor

   Detalles, 7 oct 2026, 01:33 UTC

   Cambiadas 1

   • agentstack.executedescripción
     Antes

     Bound project: agents.work_next (recipe mcp_work_loop_v1) before catalog search. discovery.search is fallback only. Mandatory session order: authenticate -> session probe auth.get_profile (alias auth.me) -> select/create project -> set context.project_id on every batch -> domain work. Playbook GET /mcp/prompts/get?name=agentstack_session_setup (recipe mcp_session_setup). Execute AgentStack operations as steps: id, action, params. Sync POST /mcp is lane mcp_batch (60000 ms) for the whole batch - not an RBAC cap. Heavy LLM actions (bots.simulate, knowledge.playground, agents.run with wait=true) : at most one per sync execute. A single heavy step is widened to ai_stream (180000 ms). Cheap discovery/list/get actions may batch (max 50 steps). Large suites: sequential executes, or options.async=true then poll discovery.job_status (REST GET /mcp/jobs/{{job_id}}). Catalog: GET /mcp/actions (see execute_budget). Cite one number: catalog_actions_public from GET /mcp/actions/summary. GET /mcp/he…

     Después

     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. 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). Sync POST /mcp is lane mcp_batch (60000 ms) for the whole batch - not an RBAC cap. One heavy LLM step per sync execute (bots.simulate, knowledge.playground, agents.run with wait=true); that step widens to ai_stream (180000 ms). Large suites: options.async=true then poll discovery.job…

   Instrucciones del servidor

   Antes

   AgentStack MCP — one tool: agentstack.execute (POST /mcp). Bound project: agents.work_next (recipe mcp_work_loop_v1) before catalog search. discovery.search is fallback only. Authenticate first: GPT/Cursor OAuth Connect (user logs in), or POST /mcp/.well-known/oauth-token grant_type=password, or MCP auth.login. If this client cannot complete OAuth, use the user's API key: header X-API-Key or Authorization: Bearer <user API key> from the profile. Session probe: auth.get_profile (alias auth.me). Bind context.project_id before domain work. If session_ready or mutation_allowed, do not log in again and do not switch_project. Then agents.work_next. Call discovery.status only when the work packet has no next_action. discovery.search for the human goal, discovery.describe for one action, preflight.check before writes. Empty lists are valid. Diagnose before repair. A timeout retries the same idempotency key. Do not call a heavy_llm action only to read state. A page at /s/{id}/ uses the hosted cookie, not operator MCP auth.login. Playbook: {hints['prompts_url']}?name=agentstack_session_setup. When discovery.search returns response_mode=workflow, run that step. Do not treat catalog_page as the command. OAuth often binds ecosystem project_id=1 — override with tenant id.

   Después

   AgentStack MCP — one tool: agentstack.execute (POST /mcp). Bound project: agents.work_next (recipe mcp_work_loop_v1) before catalog search. discovery.search is fallback only. Authenticate first: GPT/Cursor OAuth Connect (user logs in), or POST /mcp/.well-known/oauth-token grant_type=password, or MCP auth.login. If this client cannot complete OAuth, use the user's API key: header X-API-Key or Authorization: Bearer <user API key> from the profile. Session probe: auth.get_profile (alias auth.me). Bind context.project_id, then agents.work_next. If session_ready or mutation_allowed, do not log in again and do not switch_project. discovery.search only when packet.next_action is absent. discovery.describe for one action. preflight.check before writes. Empty lists are valid. Diagnose before repair. A timeout retries the same idempotency key. Do not call a heavy_llm action only to read state. A page at /s/{id}/ uses the hosted cookie, not operator MCP auth.login. Playbook: /mcp/prompts/get?name=agentstack_session_setup. When discovery.search returns response_mode=workflow, run that step. Do not treat catalog_page as the command. OAuth often binds ecosystem project_id=1 — override with tenant id.

4. 6 oct 2026, 22:22 UTC, Comprobación automática

   Inicio del seguimiento: 1 herramienta.

Preguntas frecuentes