We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

AgentStack

MCP server by AgentStack

Build and run a product's site, customer data, checkout and backend from your AI assistant through a single execute tool.

Needs an API key (Needs an API key from the vendor)Streamable HTTP

Connect to AgentStack

AgentStack needs an API key. Connect with its own URL and your key:

https://agentstack.tech/mcp

Send your key in the X-API-Key header. mcp.tc never sees or stores keys. Where to get a key

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/agentstack

About

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.

What you can do

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

  • agentstack.executeWrites

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

  • agentstack.readRead-only

    AgentStack read

Read from the live server on 21 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

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

Set up

Every client connects to agentstack.tech. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http agentstack https://agentstack.tech/mcp --header "X-API-Key: <YOUR_API_KEY>"
  1. Replace the placeholder with your key before you run it, then check it with /mcp inside Claude Code.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Use the mcp-remote bridge, which keeps the key on this computer (a connector added on claude.ai with the key under Request headers also shows up here). Open Settings → Developer → Edit Config and add:
claude_desktop_config.json
{
  "mcpServers": {
    "agentstack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://agentstack.tech/mcp",
        "--header",
        "X-API-Key: <YOUR_API_KEY>"
      ]
    }
  }
}
  1. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://agentstack.tech/mcp. Under Request headers, add X-API-Key: <YOUR_API_KEY> with your key from AgentStack, then click Add.
  2. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

VS Code

Add it to .vscode/mcp.json. VS Code asks for the key the first time and stores it securely:

.vscode/mcp.json
{
  "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
    }
  ]
}

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "agentstack": {
      "serverUrl": "https://agentstack.tech/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

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

codex mcp add can’t set the X-API-Key header, so this step is required: put this entry in ~/.codex/config.toml instead of running the command, or add its env_http_headers line to the entry the command made:

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

Codex reads the header values from the environment variables named in env_http_headers.

Gemini CLI

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

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

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

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://agentstack.tech/mcp.

Embed

Show AgentStack in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
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>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

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

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no 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>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

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

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the AgentStack card to your site.

Markdown
Add the mcp.tc card for AgentStack, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

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

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

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

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

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

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 22 Nov 2026, 11:37 UTC.

Follow AgentStack and we’ll email you when something changes.

  1. , Automatic check

    1 tool changed. Server instructions changed.

    New server instructions

    Details, 17 Nov 2026, 14:52 UTC

    Changed 1

    • agentstack.readdescription, input schema and output schema
      Before

      Read-only AgentStack MCP batch — only actions with effect read/evaluate. Same {steps, options, context} body as agentstack.execute.

      After

      Read-only batch (effect read/evaluate). Same {steps, context, options} body as agentstack.execute. Server rejects mutate steps.

      • Description of steps
        Before

        Steps; one heavy LLM per sync execute.

        After

        Same items as agentstack.execute.

      • Description of context
        Before

        session.v1; project_id required.

        After

        session.v1.

      • Description of options
        Before

        batch.v1 controls.

        After

        Same keys as agentstack.execute options.

    Server instructions

    Before

    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: GET /mcp/connect → /mcp/.well-known/oauth-authorize (PKCE), IDE Device Code POST /api/oauth2/device/authorize, 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. Packs session.v1/batch.v1: discovery.list exposes execute_budget.packs. Work Graph skill: /mcp/prompts/get?name=agentstack_work_graph (agentstack://instructions/work-graph). 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.

    After

    AgentStack MCP — one tool: agentstack.execute (POST /mcp). After VPS backend restart, first agents.work_next may fail while MCP tools import — wait ~15s and retry once (not a plan graph bug). Bound project: agents.work_next (recipe mcp_work_loop_v1) before catalog search. discovery.search is fallback only. Authenticate first: GET /mcp/connect → /mcp/.well-known/oauth-authorize (PKCE), IDE Device Code POST /api/oauth2/device/authorize, 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. Packs session.v1/batch.v1: discovery.list exposes execute_budget.packs. Work Graph skill: /mcp/prompts/get?name=agentstack_work_graph (agentstack://instructions/work-graph). 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.

  2. , Automatic check

    1 tool added and 1 tool changed. Server instructions changed.

    New server instructions

    Details, 16 Nov 2026, 05:57 UTC

    Added 1

    • agentstack.readRead-only

      Read-only AgentStack MCP batch — only actions with effect read/evaluate. Same {steps, options, context} body as agentstack.execute.

    Changed 1

    • agentstack.executedescription
      Before

      AUTH-FIRST: auth.get_profile before mutate. IDE: Connect MCP; no auth.login in chat. Unauth: auth_choices; skip discovery/work_next. Anon: create_project_anonymous; bind context.project_id. Spine: plan_get->work_next->plan_claim->plan_execute. Work Graph: work_next -> plan_claim -> plan_execute; packet.next_action first (discovery.search if empty). Prompts: session_setup, execute_budget.

      After

      AUTH-FIRST: auth.get_profile before mutate. IDE: Connect; no auth.login in chat. Unauth: auth_choices; skip work_next. Mutate: OAuth/PAT (mcp:execute). Anon: bootstrap_ack+create_project_anonymous. Spine: plan_get->work_next->plan_claim->plan_execute. WG: work_next->plan_claim->plan_execute; follow packet.next_action. Prompts: session_setup, execute_budget.

    Server instructions

    Before

    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: GET /mcp/connect → /mcp/.well-known/oauth-authorize (PKCE), IDE Device Code POST /api/oauth2/device/authorize, 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. Packs session.v1/batch.v1: discovery.list exposes execute_budget.packs. Work Graph skill: /mcp/prompts/get?name=agentstack_work_graph (skill://agentstack/work-graph). 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.

    After

    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: GET /mcp/connect → /mcp/.well-known/oauth-authorize (PKCE), IDE Device Code POST /api/oauth2/device/authorize, 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. Packs session.v1/batch.v1: discovery.list exposes execute_budget.packs. Work Graph skill: /mcp/prompts/get?name=agentstack_work_graph (agentstack://instructions/work-graph). 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.

  3. , Automatic check

    1 tool changed.

    Details, 15 Nov 2026, 02:36 UTC

    Changed 1

    • agentstack.executedescription
      Before

      AUTH-FIRST: auth.get_profile before mutate. IDE: Connect bundled MCP; no auth.login in chat. Unauth: auth_choices; skip projects/discovery/work_next. Anon: projects.create_project_anonymous on choice; bind context.project_id. Spine: agents.plan_get -> agents.work_next -> agents.plan_claim -> agents.plan_execute. Work Graph: work_next -> plan_claim -> plan_execute; follow packet.next_action (discovery.search only if empty). See prompts session_setup / execute_budget.

      After

      AUTH-FIRST: auth.get_profile before mutate. IDE: Connect MCP; no auth.login in chat. Unauth: auth_choices; skip discovery/work_next. Anon: create_project_anonymous; bind context.project_id. Spine: plan_get->work_next->plan_claim->plan_execute. Work Graph: work_next -> plan_claim -> plan_execute; packet.next_action first (discovery.search if empty). Prompts: session_setup, execute_budget.

  4. , Automatic check

    New version 0.4.27 (was 0.4.26). Reported by the server.

  5. , Automatic check

    1 tool changed.

    Details, 13 Nov 2026, 14:51 UTC

    Changed 1

    • agentstack.executedescription and output schema
      Before

      AUTH-FIRST: auth.get_profile before other actions. IDE hosts (ChatGPT/Codex): Connect on bundled connector; no auth.login in chat. Unauth: read auth_choices; skip projects/discovery/work_next. Anon: projects.create_project_anonymous only on user choice. Then context.project_id. Spine: agents.plan_get -> agents.work_next -> agents.plan_claim -> agents.plan_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. Prompts: session_setup, execute_budget.

      After

      AUTH-FIRST: auth.get_profile before mutate. IDE: Connect bundled MCP; no auth.login in chat. Unauth: auth_choices; skip projects/discovery/work_next. Anon: projects.create_project_anonymous on choice; bind context.project_id. Spine: agents.plan_get -> agents.work_next -> agents.plan_claim -> agents.plan_execute. Work Graph: work_next -> plan_claim -> plan_execute; follow packet.next_action (discovery.search only if empty). See prompts session_setup / execute_budget.

  6. , Automatic check

    1 tool changed.

    Details, 11 Nov 2026, 02:49 UTC

    Changed 1

    • agentstack.executedescription
      Before

      AUTH-FIRST: auth.get_profile before all other actions. Unauthorized -> Connect/OAuth; no projects/discovery/work_next. Anon fallback: projects.create_project_anonymous only on user choice. Then context.project_id. Spine: agents.plan_get -> agents.work_next -> agents.plan_claim -> agents.plan_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. Prompts: agentstack_session_setup, agentstack_execute_budget.

      After

      AUTH-FIRST: auth.get_profile before other actions. IDE hosts (ChatGPT/Codex): Connect on bundled connector; no auth.login in chat. Unauth: read auth_choices; skip projects/discovery/work_next. Anon: projects.create_project_anonymous only on user choice. Then context.project_id. Spine: agents.plan_get -> agents.work_next -> agents.plan_claim -> agents.plan_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. Prompts: session_setup, execute_budget.

  7. , Automatic check

    1 tool changed.

    Details, 9 Nov 2026, 08:38 UTC

    Changed 1

    • agentstack.executedescription
      Before

      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. Auth: Connect (G-A174) or Device Code, then auth.get_profile (bootstrap: include_settings false, include_subscriptions false; recipe mcp_session_setup), then context.project_id on every batch. Prompts: agentstack_session_setup, agentstack_execute_budget.

      After

      AUTH-FIRST: auth.get_profile before all other actions. Unauthorized -> Connect/OAuth; no projects/discovery/work_next. Anon fallback: projects.create_project_anonymous only on user choice. Then context.project_id. Spine: agents.plan_get -> agents.work_next -> agents.plan_claim -> agents.plan_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. Prompts: agentstack_session_setup, agentstack_execute_budget.

  8. , Automatic check

    New version 0.4.26 (was 0.4.24). Reported by the server.

  9. , Automatic check

    1 tool changed.

    Details, 3 Nov 2026, 23:44 UTC

    Changed 1

    • agentstack.executeinput schema
  10. , Automatic check

    1 tool changed.

    Details, 25 Oct 2026, 23:37 UTC

    Changed 1

    • agentstack.executeinput schema and output schema
  11. , Automatic check

    1 tool changed.

    Details, 24 Oct 2026, 01:38 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  12. , Automatic check

    1 tool changed.

    Details, 23 Oct 2026, 16:34 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  13. , Automatic check

    New version 0.4.24 (was 0.4.23). Reported by the server.

  14. , Automatic check

    1 tool changed.

    Details, 21 Oct 2026, 22:37 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  15. , Automatic check

    1 tool changed.

    Details, 18 Oct 2026, 16:29 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  16. , Automatic check

    Server instructions changed.

    New server instructions

  17. , Automatic check

    1 tool changed.

    Details, 17 Oct 2026, 07:36 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  18. , Automatic check

    New version 0.4.23 (was 0.4.22). Reported by the server.

  19. , Automatic check

    1 tool changed.

    Details, 16 Oct 2026, 16:32 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  20. , Automatic check

    1 tool changed.

    Details, 16 Oct 2026, 01:35 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  21. , Automatic check

    1 tool changed.

    Details, 15 Oct 2026, 07:35 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  22. , Automatic check

    1 tool changed.

    Details, 14 Oct 2026, 23:06 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  23. , Automatic check

    1 tool changed.

    Details, 14 Oct 2026, 10:31 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  24. , Automatic check

    1 tool changed.

    Details, 14 Oct 2026, 04:47 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  25. , Automatic check

    1 tool changed. Server instructions changed.

    New server instructions

    Details, 13 Oct 2026, 22:37 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  26. , Automatic check

    Server instructions changed.

    New server instructions

  27. , Automatic check

    1 tool changed. Server instructions changed.

    New server instructions

    Details, 11 Oct 2026, 22:38 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  28. , Automatic check

    1 tool changed.

    Details, 11 Oct 2026, 01:35 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  29. , Automatic check

    1 tool changed.

    Details, 10 Oct 2026, 19:36 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  30. , Automatic check

    1 tool changed.

    Details, 10 Oct 2026, 10:33 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  31. , Automatic check

    1 tool changed. Server instructions changed.

    New server instructions

    Details, 9 Oct 2026, 22:39 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  32. , Automatic check

    1 tool changed.

    Details, 9 Oct 2026, 19:29 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  33. , Automatic check

    New version 0.4.22 (was 0.4.21). Reported by the server.

  34. , Automatic check

    1 tool changed.

    Details, 8 Oct 2026, 13:35 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  35. , Automatic check

    1 tool changed.

    Details, 7 Oct 2026, 22:33 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  36. , Automatic check

    1 tool changed.

    Details, 7 Oct 2026, 16:36 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  37. , Automatic check

    1 tool changed. Server instructions changed.

    New server instructions

    Details, 7 Oct 2026, 01:33 UTC

    Changed 1

    agentstack.execute

    The 10 newest entries show every detail; older ones show names only.

  38. , Automatic check

    Tracking started: 1 tool.

FAQ

Can I paste mcp.tc/i/agentstack into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://agentstack.tech/mcp, so your client talks to AgentStack directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.

Does AgentStack need an API key or a sign-in?

Yes. AgentStack needs an API key, sent as the X-API-Key header. Get one from AgentStack and keep it in your client’s config, never in a shared file.

Is AgentStack a remote or a local server?

Remote. AgentStack hosts it at https://agentstack.tech/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can AgentStack do?

It has 2 tools: agentstack.execute and agentstack.read. You can run batched AgentStack actions with one execute tool, discover available actions by describing a goal and run preflight checks before write operations.

Which clients can use it?

Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. On claude.ai and Claude Desktop, add the key as a request header when you create the custom connector. ChatGPT can’t send a key, so it can’t use it.

Does mcp.tc track changes to AgentStack?

Yes. AgentStack’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read AgentStack’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with AgentStack. This page was built from AgentStack’s public metadata, last checked on 21 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.