> ## Documentation Index > Fetch the complete documentation index at: https://docs.guardway.ai/llms.txt > Use this file to discover all available pages before exploring further. # Clients > Connect Claude, Claude Code, Codex CLI, Cursor, VS Code, Devin Desktop (formerly Windsurf) or any other MCP client to Guardway MCP. ## What this is for Every client connects to the same server URL, `https://mcp.guardway.ai/mcp`. claude.ai and Claude Desktop sign in with your Guardway account. Every other client connects with a Guardway API token (it starts with `gwp_`) sent as an `Authorization: Bearer` header. In the dashboard, **Settings › Guardway MCP** has the server URL and lists the apps connected with your account. Clients other than claude.ai and Claude Desktop need a token first: see [Tokens and Scopes](https://docs.guardway.ai/guardway-mcp/tokens-and-scopes.md). ## How to configure > [tab] claude.ai and Claude Desktop > > claude.ai and Claude Desktop sign in to Guardway with your own Guardway account. There is no token to copy. > > **1. Add a custom connector** > > In Claude, open **Customize → Connectors** and choose **Add custom connector**. Enter the server URL `https://mcp.guardway.ai/mcp`. > > On a Team or Enterprise plan, an Owner of your Claude organization adds it once instead, under **Organization settings → Connectors**. Each person then connects and signs in with their own Guardway account. > > **2. Enter the OAuth client ID** > > Open **Advanced settings** and set **OAuth Client ID** to: > > ``` > client_01M6780F6HAW68T5DEQKK2KCXM > ``` > > Leave the client secret empty. > > **3. Connect and sign in** > > Choose **Connect**. Claude opens Guardway's **Connect an app** page. If you aren't signed in to Guardway, sign in first with the account you use for the dashboard; Guardway then brings you back to this page. > > **4. Check the account and continue** > > **Signed in as** shows the account Claude will act as. If it's the wrong one, choose **Use a different account**. Choose **Continue**. > > **5. Pick an organization, if asked** > > If you belong to more than one organization, a page titled **Select an organization to continue** comes next. Pick any of them: Claude still works in every organization you belong to, with your role in each, and asks you which one to use when that isn't clear. > > Claude then finishes connecting. There is no separate approval screen. > > > [!NOTE] > > > > **Added the connector with an older client ID?** If your connector's **OAuth Client ID** is `651919d4-7446-4915-9b77-da4337716e3c`, that ID is retired: remove the connector in Claude and add it again with the client ID above (if an owner added it for your Claude organization, the owner does this once). Prompt previews start off on the new connection. > [tab] Claude Code > > ```bash theme={null} > claude mcp add --transport http guardway https://mcp.guardway.ai/mcp \ > --header "Authorization: Bearer " > ``` > > Run `/mcp` in Claude Code. `guardway` shows as connected. Ask "What can this token do?" and Claude lists what the token's scopes allow. > [tab] Codex CLI > > Add the server to `~/.codex/config.toml`. Codex reads the token from an environment variable, so it stays out of the file: > > ```toml theme={null} > [mcp_servers.guardway] > url = "https://mcp.guardway.ai/mcp" > bearer_token_env_var = "GUARDWAY_TOKEN" > ``` > > Set `GUARDWAY_TOKEN` to your `gwp_` token in the shell you start Codex from, then start Codex. Run `/mcp` to check that `guardway` is listed. > [tab] Cursor > > Add the server to `~/.cursor/mcp.json` (every project) or `.cursor/mcp.json` (one project): > > ```json theme={null} > { > "mcpServers": { > "guardway": { > "url": "https://mcp.guardway.ai/mcp", > "headers": { > "Authorization": "Bearer " > } > } > } > } > ``` > > Open **Cursor Settings → MCP** and check that `guardway` is enabled and lists its tools. > [tab] VS Code > > Add the server to `.vscode/mcp.json` in your workspace. VS Code asks for the token the first time and stores it securely: > > ```json theme={null} > { > "inputs": [ > { > "type": "promptString", > "id": "guardway-token", > "description": "Guardway API token (gwp_...)", > "password": true > } > ], > "servers": { > "guardway": { > "type": "http", > "url": "https://mcp.guardway.ai/mcp", > "headers": { > "Authorization": "Bearer ${input:guardway-token}" > } > } > } > } > ``` > > Choose **Start** above the server in `mcp.json`, then open Copilot Chat in agent mode and check that the Guardway tools are listed. > [tab] Devin Desktop > > Devin Desktop was previously called Windsurf. Add the server to `~/.config/devin/mcp_config.json` (every project) or `.devin/mcp_config.json` (one project): > > ```json theme={null} > { > "mcpServers": { > "guardway": { > "url": "https://mcp.guardway.ai/mcp", > "transport": "http", > "headers": { > "Authorization": "Bearer " > } > } > } > } > ``` > > Reload the MCP servers in Devin Desktop and check that `guardway` lists its tools. > [tab] ChatGPT > > ChatGPT can't connect yet. It adds custom MCP servers with OAuth sign-in only and can't send a Guardway token, and Guardway's sign-in is only set up for Claude so far. Until then, use one of the other clients: Codex connects with a token. > [tab] Other clients > > Any client that supports remote MCP servers over Streamable HTTP and lets you set a request header can connect. Most take a JSON entry like this one; check your client's docs for the file and the exact key names: > > ```json theme={null} > { > "guardway": { > "type": "http", > "url": "https://mcp.guardway.ai/mcp", > "headers": { > "Authorization": "Bearer " > } > } > } > ``` > > Clients that only sign in with OAuth and can't send a request header can't connect yet. Then ask your client something like "Which Guardway organization am I connected to?" to confirm. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.