Connect GWC Bridge to ChatGPT

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

Menu names may look different in your language or account.

1. Who can use this route

Use ChatGPT web (https://chatgpt.com) with an account or ChatGPT Business, Enterprise, or Edu workspace that permits "Add custom MCP server". OpenAI’s Help Center documents full MCP, including write actions, for Business and Enterprise/Edu; Pro custom MCP is described as read/fetch access, and these references do not establish equivalent full access for Free or Plus. On ChatGPT Business, only workspace Admins and Owners can create and publish custom MCP server plugins (check "Workspace settings" → "Members"). On ChatGPT Enterprise and Edu, Admins and Owners can create, test, and publish custom MCP connections, and admins can use role-based access control (RBAC) under "Workspace settings" → "Permissions & roles" to grant selected members the "Create plugins with MCPs" permission to build and test connections while Admins and Owners manage workspace publication and action controls. Check the actual controls available to your account; GWC cannot change vendor eligibility or workspace policy.^[2]

2. Prepare the computer

On the target computer, use an official supported release of GWC Studio, where available for your operating system, or install GWC for VS Code in Visual Studio Code.
Open it, sign in to your own GWC account, link the intended computer, and keep the GWC component running and online. Authorize this same GWC account in the connector.
Share a non-sensitive folder first and review this app’s actual Change files and Commands permissions on that PC, not only instructions written in a chat prompt. Folder boundaries, protected paths, connection grants, least-privilege defaults, and PC confirmations remain separate server-enforced controls.
Maintain an active GWC Personal Connect Pass (Connect Pass) for remote authorization and tool actions. GWC refuses unsigned or unentitled callers independently of your ChatGPT subscription. Seeing a tool list does not prove access, and adding a remote connector does not install the PC component.

3. Server address and OAuth

Paste this exact remote HTTPS MCP address into the connector’s server URL field:

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

Use individual OAuth 2.1 sign-in with PKCE (S256) and automatic Client ID Metadata Documents (CIMD) discovery (client_id_metadata_document_supported: true). Unauthenticated requests to https://mcp.gwc-corp.com/mcp return 401 Unauthorized with a WWW-Authenticate resource_metadata header pointing to Protected Resource Metadata (https://mcp.gwc-corp.com/.well-known/oauth-protected-resource, RFC 9728) and Authorization Server https://api.gwc-corp.com. Leave "Advanced OAuth settings" ("Client ID" and "Client Secret") blank and do not choose "No authentication": GWC uses public clients (none) with CIMD rather than Dynamic Client Registration (DCR) or static secrets, and entering static credentials overrides automatic CIMD discovery. Never paste GWC passwords, access/refresh tokens, or API keys into prompts or request headers.^[3]

Manual setup is off by default. When enabled, the default client-metadata hosts are chatgpt.com, openai.com and claude.ai. The Claude host is exactly claude.ai; claude.com, other subdomains and explicit ports (even :443) are not admitted by that default. If GWC has a configured host list, it replaces these defaults.

When manual support is enabled, GWC advertises and accepts offline_access (refresh_token grant support) and retains it when requested in the OAuth flow. Existing refresh tokens rotate; the client must use each replacement token. This scope does not add file, command or other PC permissions. The PC must stay online for tool actions. A revoked or invalid connection needs a new official sign-in.

Optional plugin ZIP setup: If the GWC Bridge setup page offers the ChatGPT plugin ZIP, download it there first. In ChatGPT choose Plugins > Add > Upload plugin and select the ZIP; open GWC Bridge > Connect and sign in with the same GWC account as the computer. If prompted to Open in desktop app, finish there. Choose this route or Add custom MCP server below, not both.

4. Personal setup

Open ChatGPT web, open "Plugins" from the navigation sidebar, and select "+" → "Add custom MCP server". You do not need to turn on a separate "Developer Mode" toggle first.
Enter the name GWC Bridge (and an optional description), then under "Connection" choose "Server URL" and enter https://mcp.gwc-corp.com/mcp.
Set "Authentication" to "OAuth" and leave "Advanced OAuth settings" ("Client ID" and "Client Secret") blank so ChatGPT automatically discovers GWC’s OAuth metadata via Client ID Metadata Documents (CIMD). Do not enter a client secret or use "No authentication".
Review the per-server risk warning, select "I understand and want to continue", and select "Create as a plugin". Complete the GWC sign-in and consent prompt in your browser when redirected, then review the discovered tools and metadata on the plugin details page.
Open the item in your personal "Plugins" (or switch the homepage from "Chat" to "Work"), start a new conversation on the web, and select "+" in the message composer or type @ / / to select GWC Bridge.
Start with a read-only check (such as identifying the available computer and listing filenames in your authorized test folder without reading file contents, editing files, or running commands). In "Settings" → "Plugins" or "Settings" → "Apps", keep write and command confirmations enabled; ChatGPT’s prompt settings never override or expand the folder and command permissions enforced by GWC on the PC.^[1]

5. Organization or workspace setup

An authorized Admin or Owner checks workspace permissions ("Workspace settings" → "Members" on Business, or "Workspace settings" → "Permissions & roles" on Enterprise/Edu where RBAC can grant "Create plugins with MCPs") and creates GWC Bridge through "Plugins" with https://mcp.gwc-corp.com/mcp and blank-credential "OAuth".
Test privately in a new web conversation before workspace rollout: verify tool selection, arguments, authorization boundaries, and a read-only folder listing on a non-sensitive test folder. Never use production data, file deletion, package installation, deployment, or broad shell commands as your initial connection test.
From the GWC Bridge plugin details page (or "Admin console" → "Plugins" → "Manage Legacy Apps" → "Drafts" / "Workspace Settings" → "Apps" → "Drafts" → "Publish"), an Admin or Owner publishes the plugin to the workspace or designated Enterprise/Edu roles after reviewing action controls. Workspace publication shares the plugin inside your organization only and is not an OpenAI public-directory submission.
Each workspace member opens "Settings" → "Plugins" (or "Settings" → "Apps"), selects GWC Bridge → "Connect", and signs in with their own GWC account (with an active Connect Pass and online PC). Connecting a GWC account does not switch the user’s active ChatGPT workspace; never share administrator credentials or paste tokens into chat.

Published or connected MCP plugins cache their tool definitions until refreshed. When GWC adds or updates tools, an authorized admin or user can open the GWC Bridge details page in "Plugins" / "Apps" settings and select "Refresh" to update its tools, descriptions, and instructions without deleting it (if .well-known OAuth discovery metadata changes, recreate the plugin). On Enterprise and Edu, admins and owners can also enable or disable individual app actions after publishing.^[2]

To remove access, open "Settings" → "Plugins" (or "Settings" → "Apps"), select GWC Bridge, and choose "Disconnect" for an individual account, or disable/remove the published plugin from the workspace’s "Plugins" (or "Manage Legacy Apps") administration page. Disconnecting stops future remote tool calls without deleting prior chat transcripts or automatically terminating a long-running local process already started on the computer; always check GWC Studio or GWC for VS Code on the PC before retrying an interrupted command or file edit.^[2]

6. Other clients

OpenAI documents custom MCP workspace and personal connections for ChatGPT on the web. Do not assume ChatGPT mobile apps or native desktop apps provide the same manual MCP setup or execution path; continue using ChatGPT in a desktop browser rather than repeatedly reconnecting from mobile apps.^[2]

If your workspace shows the legacy custom-app administration view ("Admin console" → workspace → "Plugins" → "Manage Legacy Apps", or "Workspace settings" → "Apps" → "Create" with "Scan Tools" and "Workspace Settings" → "Apps" → "Drafts"), use it only where your workspace presents that interface. Do not mix steps between the current "Plugins" interface and the legacy "Apps" interface, and do not assume a missing legacy menu means GWC has been approved or rejected.^[2]

7. Troubleshooting

What you may see	Next step
Setup control missing — "Add custom MCP server"	Confirm you are on ChatGPT web, inside the intended Business, Enterprise, or Edu workspace (or eligible account), and hold an Admin/Owner role or an Enterprise/Edu role granted "Create plugins with MCPs".
`invalid_client` — manual Client ID/Secret entered or `client_id host is not allowed`	Leave "Client ID" and "Client Secret" blank when creating the plugin so ChatGPT uses Client ID Metadata Documents (`client_id_metadata_document_supported: true` on `chatgpt.com` / `openai.com`), and ask GWC to verify manual enablement and the allowed host list. GWC does not use static secrets or Dynamic Client Registration (DCR).
`invalid_request` — `redirect_uri is not registered by the client`	ChatGPT uses `https://chatgpt.com/connector_platform_oauth_redirect` (and `https://chatgpt.com/connector/oauth/{callback_id}` when callback-specific redirects apply) via its CIMD metadata. Ensure no proxy or firewall rewrites `redirect_uri` or strips the `resource` parameter.
`invalid_scope` — `Requested scope is not supported` or connection opens with no tools	Confirm the Server URL is `https://mcp.gwc-corp.com/mcp`, OAuth sign-in completed, requested scopes match GWC’s enabled metadata, and `https://mcp.gwc-corp.com/.well-known/oauth-protected-resource` is reachable from OpenAI’s connector egress IPs (`https://openai.com/chatgpt-connectors.json`).
`invalid_grant` / `GRANT_REVOKED` or repeated sign-in prompts after expiry	GWC’s authorization server (`https://api.gwc-corp.com`) supports rotating `refresh_token` grants with PKCE (`S256`). If an authorization was revoked or ChatGPT cached an older app configuration before refresh metadata was present, recreate or reconnect the plugin through the official UI; never replay or share a refresh token.
`CONNECT_PASS_REQUIRED` / `connect_pass_required` — `Your GWC account does not currently have an active Connect Pass entitlement.`	Verify that the signed-in GWC account has an active GWC Personal Connect Pass (Connect Pass). Workspace publication or a ChatGPT subscription does not grant a Connect Pass.
`PC_OFFLINE` / `DEVICE_NOT_ONLINE`	Confirm the target computer is online, GWC Studio or GWC for VS Code is running and signed in to the same GWC account, and do not silently switch to another computer.
`ROOT_NOT_SHARED` / `PATH_PROTECTED`	Confirm the folder is shared in GWC Bridge on the target PC. The PC owner can review that exact folder and grant; protected paths remain unavailable.
`SCOPE_NOT_GRANTED` / `APPROVAL_DENIED` / `CLIENT_ACCESS_DISABLED` (read works, write or command refused)	Check both sides independently: (1) whether Enterprise/Edu workspace action controls or ChatGPT confirmation prompts blocked the call, and (2) whether Change files or Commands is enabled for that folder in GWC Studio / GWC for VS Code on the PC.
`UPDATE_REQUIRED` or tools fail after a GWC Bridge update	Update the installed GWC component through its official supported channel, then open the GWC Bridge details page in ChatGPT "Plugins" / "Apps" settings and select "Refresh" to pull updated tool schemas.
`RATE_LIMITED` or a file edit / command timed out	Pause before retrying a status read, and inspect the file or process state on the computer first; a network timeout does not prove the action did not run on the PC.
`GWC_BRIDGE_PROTOCOL_ERROR` (HTTP 500, `-32603`) — `GWC Bridge could not complete this request. Check the connection and try again.`	Check the connection and the earlier action’s result on the PC before retrying. When contacting support, record the timestamp, workspace name, tool name, error code, and non-sensitive request ID without passwords, tokens, or private file contents.
`Internal server error` / `INTERNAL` / `temporarily_unavailable` / HTTP 503	Ask GWC to check service configuration/availability. Setup may display a general error; other tool errors and outages have separate messages.

8. Privacy and permissions

ChatGPT receives the outputs returned by authorized GWC Bridge tool calls, such as folder listings, requested file contents, and command output; both content and structuredContent returned by a tool enter the model’s conversation context, so do not tell users that no file contents ever leave the PC when they ask ChatGPT to read files or run commands. When ChatGPT invokes a tool, it sends the tool arguments derived from the conversation to GWC Bridge and your connected computer; limit shared folders and command permissions in GWC Studio or GWC for VS Code to what is needed for the task.

For ChatGPT Business, Enterprise, and Edu, OpenAI states that workspace data—including information accessed through connected plugins and apps—is not used to train OpenAI models by default, while your organization’s retention policies and GWC’s data handling for authenticated relay requests still apply. Connecting GWC Bridge in ChatGPT authorizes only that ChatGPT connection and does not share your ChatGPT conversations with any other AI client; if another assistant is separately connected to the same computer and shared folder, it can only observe changes written to disk in that shared folder.

9. Official references

For the setup steps and account requirements, see these official references. Your GWC connection must still be enabled and working.