MCP clients
Configure supported coding and assistant clients from the MCP Server screen.
Copy the configuration shown in AgentStack's MCP Server screen for the client you are connecting. The dashboard renders guidance for Cursor, Claude Code, Claude Desktop, Codex, Gemini CLI, VS Code, Windsurf, Zed, OpenCode, Warp, v0, Kiro, and Roo Code, as well as a generic direct-URL fallback. Client configuration formats change, so the live dashboard snippet is more reliable than a hand-transcribed example.
Some clients connect to the direct HTTP endpoint; others use a compatible relay. Complete the OAuth flow in the client, confirm the consented scopes, then run a small read-only request to verify the authorized user and organization. Keep the copied configuration in the client’s appropriate settings location and never substitute a REST API key for an MCP OAuth token.
When troubleshooting, inspect the dashboard's Authorized Clients and recent MCP calls, then verify that the selected organization is the intended one. To change access, remove or reconfigure the local client entry and re-authorize; the dashboard does not currently offer a server-side client-revoke control.