MCP clients
Configure supported coding and assistant clients from the MCP Server screen.
Copy the configuration for your client from the MCP Server screen in AgentStack. The dashboard shows guidance for Claude Code, Claude Desktop, and Codex. It also shows a generic direct-URL option for every other client, with an mcp-remote fallback for stdio-only clients. Client configuration formats change often. Use the live dashboard snippet, not a hand-transcribed example.
Some clients connect to the direct HTTP endpoint. Other clients use a compatible relay. Complete the OAuth flow in the client. Confirm the consented scopes. Then run a small read-only request to confirm the authorized user and organization. Keep the copied configuration in the correct settings location for the client. Do not substitute a REST API key for an MCP OAuth token.
To troubleshoot a problem, check the dashboard's Authorized Clients list and the recent MCP calls. Then confirm that the selected organization is correct. To change access, remove or reconfigure the local client entry. Then complete the OAuth flow again. To cut a client off at once, select Revoke on its row in the Authorized Clients list and confirm. The client loses access at once and must be authorized again before it can connect. Revoke removes only the authorizations that you granted, not a teammate's.