Clients

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.

How to configure

claude.ai and Claude Desktop sign in to Guardway with your own Guardway account. There is no token to copy.

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.

Enter the OAuth client ID

Open Advanced settings and set OAuth Client ID to:

client_01M6780F6HAW68T5DEQKK2KCXM

Leave the client secret empty.

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.

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.

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.

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.

claude mcp add --transport http guardway https://mcp.guardway.ai/mcp \
  --header "Authorization: Bearer <your gwp_ token>"

Run /mcp in Claude Code. guardway shows as connected. Ask “What can this token do?” and Claude lists what the token’s scopes allow.

Add the server to ~/.codex/config.toml. Codex reads the token from an environment variable, so it stays out of the file:

[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.

Add the server to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "guardway": {
      "url": "https://mcp.guardway.ai/mcp",
      "headers": {
        "Authorization": "Bearer <your gwp_ token>"
      }
    }
  }
}

Open Cursor Settings → MCP and check that guardway is enabled and lists its tools.

Add the server to .vscode/mcp.json in your workspace. VS Code asks for the token the first time and stores it securely:

{
  "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.

Devin Desktop was previously called Windsurf. Add the server to ~/.config/devin/mcp_config.json (every project) or .devin/mcp_config.json (one project):

{
  "mcpServers": {
    "guardway": {
      "url": "https://mcp.guardway.ai/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer <your gwp_ token>"
      }
    }
  }
}

Reload the MCP servers in Devin Desktop and check that guardway lists its tools.

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:

{
  "guardway": {
    "type": "http",
    "url": "https://mcp.guardway.ai/mcp",
    "headers": {
      "Authorization": "Bearer <your gwp_ token>"
    }
  }
}

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.

Getting Started

Platform

Guardway MCP

Gateway

Inventory

Endpoint AI Risk

Resources

API Reference

What this is for

How to configure

​What this is for

​How to configure

What this is for

How to configure