Connect GWC Bridge to Claude

Connect GWC Bridge to Claude as a custom connector so Claude can work with the files and commands you permit on your own PC.

Menu names may look different in your language or account. GWC Bridge lets Claude work with permitted files and commands on your own PC, where GWC for VS Code or GWC Studio is running. This guide uses Claude’s custom connector setup; adding a server manually does not mean Anthropic has reviewed or endorsed it.

1. Who can use this route

Claude supports custom remote connectors on Free, Pro, Max, Team, and Enterprise plans. Free accounts can have one custom connector. On Team plans, an Owner or Primary Owner must add GWC Bridge to the organization first; on Enterprise plans, an Owner, Primary Owner, or a member with a custom role that includes "Manage access to Libraries" must add it first.^[1]

Claude Code requires separate Claude Code eligibility through a supported subscription or organization arrangement. A Free Claude account alone does not include Claude Code access.^[3]

2. Before you start

Have your GWC account ready, an active Connect Pass, and GWC for VS Code or GWC Studio running and connected on the PC you intend Claude to use.
Sign in to the same GWC account on your PC and when authorizing the Claude connector; adding GWC Bridge’s URL in Claude does not install the PC component.
Review the files, folders, and command permissions you intend to expose on that PC, and start with the smallest access needed.
GWC Bridge refuses callers who are not authenticated or entitled; adding its URL or seeing a tool list does not bypass those checks.

3. Server address and OAuth

Use this server address:

https://mcp.gwc-corp.com/mcp

GWC Bridge authenticates automatically using Claude’s published Client ID Metadata Document (CIMD) and PKCE. You do not need—and must not enter—an OAuth Client ID or OAuth Client Secret. Never paste passwords, access tokens, or client secrets into a Claude conversation or request headers.^[4]

Optional plugin ZIP setup: If the GWC Bridge setup page offers the Claude plugin ZIP, download it there first. In Claude choose Customize > Plugins > Add > Upload plugin and select the ZIP; open GWC Bridge > Connectors > Connect and sign in with the same GWC account as the computer. Choose this route or Add custom connector below, not both.

4. Personal setup (Free, Pro, or Max)

Sign in to the Claude account you intend to use at claude.ai (or in Claude Desktop) and open "Customize" → "Connectors".
Click "+ Add" (or "+") → "Add custom connector". In the unified menu layout, click "Add" → "Custom" → "Web".
Name the connector GWC Bridge and enter https://mcp.gwc-corp.com/mcp; if the dialog shows an "Advanced settings" section for an optional OAuth Client ID and OAuth Client Secret, leave both fields blank.
Click "Continue" (or "Add" if using the single-step dialog) to review the detected authentication settings: under "Authentication", keep "Sign in now" (do not select "No sign in"); under "OAuth client", keep "Use Claude's published identity (Recommended)" (do not select "Register automatically" because GWC Bridge does not use Dynamic Client Registration, and do not select "Use your own OAuth client"); and leave "Request headers" empty.
Click "Add" to finish creating the connector, then click "Connect" if sign-in has not already started, and complete GWC’s browser sign-in and consent flow.
Confirm that GWC Bridge shows as connected in "Customize" → "Connectors", open "+" → "Connectors" (or the "Search and tools" menu) in a conversation to enable GWC Bridge, leave file changes and commands set to require approval until you are comfortable with the access, and run a read-only first check (Use GWC Bridge to show which of my computers and shared folders are available. Do not change files or run commands.), check the results, not just the connected label.^[1]

5. Organization setup (Team or Enterprise)

An organization "Owner" or "Primary Owner" (or on Enterprise, someone with a custom role that includes "Manage access to Libraries") opens "Organization settings" → "Connectors" → "Add" → "Custom" → "Web" (or chooses "Add custom connector").
Enter the name GWC Bridge and the server URL https://mcp.gwc-corp.com/mcp, then click "Continue".
Keep the detected authentication settings ("Sign in now" and "Use Claude's published identity (Recommended)"), leave "Request headers" and any custom OAuth client credential fields blank, and click "Add".
After the connector is added to the organization, each member opens "Customize" → "Connectors", finds GWC Bridge (marked with a "Custom" label), clicks "Connect" to sign in with their own GWC account, and enables it in "+" → "Connectors" (or "Search and tools").

Making the connector available to an organization does not sign members in automatically.^[1]

6. Mobile and Claude Code

Set up and authenticate GWC Bridge on Claude web or Claude Desktop first, then sign in to the same Claude account—and the same organization, where applicable—in the Claude iOS or Android app. Web connectors work on Claude Mobile once configured on your account. Installing connectors directly on mobile is currently in beta—Claude Desktop and web remain the primary path for setting up custom connectors.^[2]

In Claude Code, first check /mcp: if you sign in with your Claude account, the connector you added on claude.ai may already be loaded automatically, so avoid adding a duplicate CLI entry if the account connector is already present. To add (or later remove) GWC Bridge directly via the CLI, run in your terminal:^[3]

claude mcp add --transport http --scope user gwc-bridge https://mcp.gwc-corp.com/mcp
claude mcp remove gwc-bridge --scope user

After adding the server, start Claude Code, run /mcp, select gwc-bridge, choose "Authenticate", and finish the GWC sign-in flow in your browser. The user scope makes this server available across all of your projects on that machine. Verify the server status and run the read-only first check above. Your organization may restrict which MCP servers Claude Code can load; do not attempt to bypass organization policies by altering authentication or switching accounts.^[3]^[4]

7. What Claude can see and how to disconnect

GWC Bridge is more than a list of tool names. When an authorized tool reads a file or returns command output, that content is sent to Claude. A connector can also expose MCP resources and workflow prompts. The actions available through GWC Bridge depend on your GWC permissions and PC folder policies; Claude’s tool permission controls can restrict which tools Claude invokes, but cannot grant access that GWC Bridge refuses. Review approval prompts carefully, especially before editing files, deleting files, or running commands. Do not assume that remote connector traffic stays strictly local: across claude.ai, Claude Desktop, Cowork, and Claude Mobile, Claude connects to remote MCP servers from Anthropic’s cloud infrastructure. Adding the URL never grants automatic screen control, unrestricted file access, or unapproved command execution—only the shared folders and capabilities you have authorized in GWC are available.

To disconnect or remove GWC Bridge, open "Customize" → "Connectors" and select GWC Bridge:

"Disconnect" signs Claude out of GWC Bridge while keeping the connector in your list.
"Remove" / "Delete" (from the connector’s menu) removes a personal custom connector from your account.
"Organization-wide removal" on Team and Enterprise plans must be performed by an authorized Owner in "Organization settings" → "Connectors".
Turning off the connector in a conversation’s "+" → "Connectors" or "Search and tools" menu only disables it for that conversation; if the connector is synced to Claude Code from your claude.ai account or provided by your organization, manage or remove it in Claude’s connector settings (or toggle it off for yourself in /mcp).

8. Troubleshooting

Symptom	What to check
No option to add a custom connector	On a Free plan, check whether your single custom-connector slot is already in use. On Team or Enterprise, ask an Organization Owner (or an Enterprise admin with "Manage access to Libraries") to add it under "Organization settings" → "Connectors".
GWC Bridge is absent from the Connectors Directory	Use the custom connector URL flow (`https://mcp.gwc-corp.com/mcp`). Manual setup does not require a directory listing.
Setup asks for an OAuth Client ID or OAuth Client Secret	Leave optional Client ID and Client Secret fields in "Advanced settings" blank. Never guess or enter static client credentials.
OAuth client registration fails	In the two-step setup dialog, ensure "OAuth client" is set to "Use Claude's published identity (Recommended)", not "Register automatically" (GWC Bridge does not use Dynamic Client Registration) or "Use your own OAuth client".
Sign-in finishes, but GWC refuses access	Verify that you signed in with the intended GWC account and that its Connect Pass is active. Do not select "No sign in" to bypass the refusal.
“Couldn’t reach the MCP server”	Recheck that the URL is `https://mcp.gwc-corp.com/mcp`. A temporary service outage, OAuth discovery timeout, or network firewall/WAF block between Anthropic’s IP ranges and the server can cause this error. Report the exact error and reference ID to GWC support.
Connected, but Claude does not use the tools	Check that GWC Bridge is enabled in the conversation’s "+" → "Connectors" / "Search and tools" menu and that individual tools are not disabled. Ask explicitly for a GWC Bridge action.
The PC or a folder is unavailable	Confirm the intended PC is online, GWC Studio or GWC for VS Code is running and connected, and the folder is shared for this connection. Do not switch to another PC without verifying it is the intended target.
Reads work, but edits or commands fail	Check both Claude’s tool approval settings and the folder’s "Change files" / "Commands" permissions in GWC. Treat a permission refusal as a policy restriction to resolve, not a transient failure to retry blindly.
Mobile does not show the connector	Confirm you are signed in to the same Claude account and organization on mobile, and complete initial custom connector setup on Claude web or Desktop first.
Claude Code does not show a web-added connector	Run `/status` to check your login method. Logging in with an API key or a different provider profile prevents claude.ai account connectors from loading. Check organization MCP policies in `/mcp` as well.
Claude Code needs authentication or the browser does not open	Run `/mcp`, select `gwc-bridge`, and choose "Authenticate". Copy and open the authorization URL displayed in the terminal if your browser does not launch automatically.
A file change or command times out	Do not assume the action failed completely. Inspect the current file state or recent activity before repeating a state-changing operation.

When contacting GWC support, include the Claude app/surface you are using, your Claude plan type, the step where the issue occurred, and any error message or reference ID. Never send passwords, bearer tokens, client secrets, or private file contents.

9. Official references

For the current setup steps, see these official guides: