AgentStack

Über den Server

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.

Was du damit machen kannst

• 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

Tools 1

• agentstack.executeKann löschen

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

Am 7. Okt. 2026 vom laufenden Server gelesen. „Liest nur“, „Schreibt“ und „Kann löschen“ sind Hinweise, die der Server selbst angibt; dein Client entscheidet, ob er vor dem Ausführen eines Tools nachfragt.

Beispiel-Prompts

• 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.

Einrichtung

Jeder Client verbindet sich mit agentstack.tech. Wähl deinen; die Seite merkt sich deine Wahl.

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>"
      }
    }
  }
}

Einbinden

Zeig AgentStack in einem README oder auf deiner Website. Jede Einbindung verlinkt auf diese Seite, nutzt die eigene URL des Servers und setzt keine Cookies. So funktionieren Einbindungen

Karte, iframe und JSON sind auf Englisch. Häng ?lang=it, fr, de oder es an ihre Adresse an, um eine andere Sprache zu bekommen.

README-Badge Website-Karte iframe JSON KI-Prompt

README-Badge

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>

Es folgt dem hellen oder dunklen Modus der Lesenden. Hänge ?theme=light oder ?theme=dark an, um ihn festzulegen, oder ?style=compact, um das Zeichen ohne Schriftzug zu zeigen.

Website-Karte

HTML

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

Die Karte erscheint dort, wo das Tag steht. Füge dem Tag data-theme="dark" oder data-size="compact" hinzu, um sie zu ändern. Die Datei enthält alles, was sie braucht, stellt also keine weiteren Anfragen und setzt keine 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>

Nutze es auf Seiten, die keine Skripte erlauben. Hänge ?theme=light oder ?theme=dark an die Adresse an, um die Farben festzulegen.

JSON

Der Eintrag als Daten für deine eigenen Seiten und Tools: Name, Kurzbeschreibung, die eigene URL des Servers, Tools und die „Add to“-Links. Jede Website kann ihn lesen (CORS ist offen).

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

Was jedes Feld bedeutet

KI-Prompt

Füg ihn in einen KI-Coding-Assistenten wie Claude Code oder Cursor ein, und er baut die Karte von AgentStack in deine Website ein.

Markdown

Füge meiner Website die mcp.tc-Karte für den MCP-Server AgentStack hinzu. Es ist ein einziges statisches Skript: kein Build-Schritt, kein Paket zu installieren, keine Cookies.

Setz dieses Tag dorthin, wo die Karte erscheinen soll. Die Karte erscheint direkt davor:

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

Um sie woanders zu zeigen, setz dort diesen Platzhalter ein und lade dasselbe Skript nur einmal, zum Beispiel vor `</body>`. Lass den Link darin stehen: Besucher ohne JavaScript sehen ihn.

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

Optionen:
- `data-theme="light"` oder `"dark"` am Tag oder Platzhalter legt die Farben fest. Ohne das Attribut folgt die Karte dem hellen oder dunklen Modus der Besucher.
- `data-size="compact"` ergibt eine kleinere Karte ohne Kurzbeschreibung.
- Die CSS-Variable `--mcptc-max-width` am Platzhalter oder einem Elternelement legt die Breite fest (Standard `520px`).
- `?lang=` in der Skript-URL legt die Sprache der Karte fest: `en`, `it`, `fr`, `de` oder `es`.

Wenn die Website eine Content Security Policy hat, erlaube `script-src https://mcp.tc` und `img-src data:` (das Icon ist eingebettet).

Für ein README oder andere Markdown-Dokumentation nimm stattdessen das Badge:

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

Referenz: https://mcp.tc/de/embed

Änderungsverlauf

Wir lesen die Tool-Liste dieses Servers alle 3 Stunden und halten fest, was sich ändert. Zuletzt gelesen: 8. Okt. 2026, 07:29 UTC.

1. 7. Okt. 2026, 22:33 UTC, Automatische Prüfung

   1 Tool geändert.

   Details, 7. Okt. 2026, 22:33 UTC

   Geändert 1

   • agentstack.executeEingabeschema und Ausgabeschema
     • Beschreibung von context
       Vorher

       keine

       Nachher

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

     • Beschreibung von options
       Vorher

       keine

       Nachher

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

2. 7. Okt. 2026, 16:36 UTC, Automatische Prüfung

   1 Tool geändert.

   Details, 7. Okt. 2026, 16:36 UTC

   Geändert 1

   • agentstack.executeBeschreibung
     Vorher

     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…

     Nachher

     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. Okt. 2026, 01:33 UTC, Automatische Prüfung

   1 Tool geändert. Server-Anweisungen geändert.

   Neue Server-Anweisungen

   Details, 7. Okt. 2026, 01:33 UTC

   Geändert 1

   • agentstack.executeBeschreibung
     Vorher

     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…

     Nachher

     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…

   Server-Anweisungen

   Vorher

   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.

   Nachher

   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. Okt. 2026, 22:22 UTC, Automatische Prüfung

   Beginn der Beobachtung: 1 Tool.

Häufige Fragen