# AgentStack MCP server > Build and run a product's site, customer data, checkout and backend from your AI assistant through a single execute tool. - Listing: https://mcp.tc/i/agentstack - Connect: use the server's own URL `https://agentstack.tech/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: API key - Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops) - Vendor: AgentStack - Homepage: - Docs: ## 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 it 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 (1) - `agentstack.execute`: Run AgentStack operations as steps with action and params, within a project context; can write or… (can modify or delete data) ## 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." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http agentstack https://agentstack.tech/mcp --header "X-API-Key: " ``` 2. 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`: ```json { "mcpServers": { "agentstack": { "command": "npx", "args": [ "-y", "mcp-remote", "https://agentstack.tech/mcp", "--header", "X-API-Key: " ] } } } ``` 2. 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: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://agentstack.tech/mcp`. Under **Request headers**, add `X-API-Key: ` with your key from AgentStack, then click **Add**. 3. 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 [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "agentstack": { "url": "https://agentstack.tech/mcp", "headers": { "X-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`: ```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`: ```json { "mcpServers": { "agentstack": { "serverUrl": "https://agentstack.tech/mcp", "headers": { "X-API-Key": "" } } } } ``` 2. Refresh the MCP server list in Cascade. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash 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`: ```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 ```bash gemini mcp add --transport http --header "X-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. ```json { "mcpServers": { "agentstack": { "type": "http", "url": "https://agentstack.tech/mcp", "headers": { "X-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`. ## Recent changes - 2026-10-07 22:33 UTC: 1 tool changed. Source: automatic check. Changed: agentstack.execute. - 2026-10-07 16:36 UTC: 1 tool changed. Source: automatic check. Changed: agentstack.execute. - 2026-10-07 01:33 UTC: 1 tool changed. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Changed: agentstack.execute. - 2026-10-06 22:22 UTC: Tracking started: 1 tool read. Source: automatic check. More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/agentstack#history (Atom feed: https://mcp.tc/i/agentstack/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review. ## Details - Server version: 0.4.21 - MCP protocol version: 2026-07-28 - Last checked: 2026-10-07 (reachable) - Listed: 2026-10-06 - Updated: 2026-10-07 --- Source: https://mcp.tc/i/agentstack (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report