MCP Server

AgentStack exposes a Model Context Protocol server scoped to your active organization. Once connected, your MCP client (Cursor, Claude Code, Claude Desktop, Codex, Gemini CLI, and others) can read agents, sources, and conversations and perform admin operations like creating agents, running tests, and adding sources — without you threading an organization ID through every call.

Server URL

Use the streamable HTTP endpoint:

https://www.agentstack.build/api/mcp

The exact URL is shown on the MCP Server settings page, where you can also copy ready-made configs for each client.

Authentication

OAuth via Better Auth. The first time a client connects, AgentStack opens a browser sign-in. You approve the scopes (read-only or write), and the client stores a refresh token. Tokens are scoped to your user account; the active organization at the time of authorization determines which org the tools operate against.

Install

The settings page renders the right snippet for your client. Quick reference:

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "agentstack": {
      "url": "https://www.agentstack.build/api/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http agentstack https://www.agentstack.build/api/mcp -s user

Claude Desktop

stdio-only, so route through mcp-remote. Add to claude_desktop_config.json:

{
  "mcpServers": {
    "agentstack": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.agentstack.build/api/mcp"]
    }
  }
}

Codex

Add to ~/.codex/config.toml:

[mcp_servers.agentstack]
command = "npx"
args = ["-y", "mcp-remote", "https://www.agentstack.build/api/mcp"]

Gemini CLI

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "agentstack": {
      "httpUrl": "https://www.agentstack.build/api/mcp"
    }
  }
}

Other clients

VS Code, Windsurf, OpenCode, Zed, Warp, v0, Kiro, Roo Code and most other MCP-compatible clients accept the standard mcpServers block. Use the direct URL form first; fall back to the mcp-remote relay if your client only supports stdio.

What you get

• Read agents, sources, and conversations.
• Create and update agents, run agent tests, add URL or text sources, and restore soft-deleted records.
• Approve read-only or write access during browser sign-in.

Troubleshooting

• Client says "not authenticated": revisit the MCP Server page and confirm your client is listed under Authorized Clients. Re-running the install command re-triggers the OAuth flow.
• stdio client can't connect to streamable HTTP: use the mcp-remote form shown above. It runs locally and proxies to the AgentStack endpoint.
• Wrong organization: switch the active org in the dashboard, then re-authorize the client. The org context is captured at authorization time.