GWC Bridge
Your AI apps.Your computer.
GWC Bridge is our MCP product for ChatGPT, Claude, Gemini, Grok and Muse. Your desktop controls which folders are shared.
You choose the computer and folders AI apps can access.
BEFORE YOU START
Prepare the computer first.
Before buying or starting a Connect Pass trial, check ChatGPT Plugins for Add custom MCP server or Upload plugin. These depend on your ChatGPT plan and workspace role. Business needs Admin/Owner; Enterprise/Edu needs an authorized role. Pro may be read/fetch-only; full MCP on Free/Plus is not established by the guide. Connect Pass does not change ChatGPT permissions.
- 1Have an active Connect Pass on the GWC account you will authorize.
- 2Install and run GWC Studio or GWC for VS Code on the intended computer. Sign in and keep it online.
- 3Share your project folders on that computer, and review their Change files and Commands permissions.
- 4Set up the plugin or connect the MCP server for ChatGPT, Claude, Gemini, Grok or Muse. The guides below show the options for each.
GWC Bridge
You choose what AI can access.
Install GWC Studio or GWC for VS Code on your computer. Then connect GWC Bridge in ChatGPT, Claude, Gemini, Grok or Muse. One GWC approval covers every folder shared on your account's computers and all server-supported permissions; control folders on the desktop.
CONNECT YOUR AI
Choose your AI app.
Follow the guide for your AI app to add GWC Bridge as a plugin or MCP server.
ChatGPT
On the ChatGPT Plugins page, Upload plugin archive using the portable OAuth ZIP or Add custom MCP server. If ChatGPT web offers Open in desktop app, continue in ChatGPT desktop; custom MCP stays on the same page.
Custom MCP controls depend on your ChatGPT plan and workspace policy. Business Admins/Owners create plugins; Enterprise/Edu roles require the appropriate plugin permission and publishing controls. Confirm eligibility in ChatGPT first.
Before buying or starting a Connect Pass trial, check ChatGPT Plugins for Add custom MCP server or Upload plugin. These depend on your ChatGPT plan and workspace role. Business needs Admin/Owner; Enterprise/Edu needs an authorized role. Pro may be read/fetch-only; full MCP on Free/Plus is not established by the guide. Connect Pass does not change ChatGPT permissions.
ChatGPT — Full setup and troubleshooting guide
ChatGPT — Detailed manual setup guideSetup overview
- 1
Prepare your computer for GWC Bridge
Use the same GWC account, keep GWC Studio or GWC for VS Code online, confirm your Connect Pass, and share your project folders.
- 2
Choose a ChatGPT Plugins setup method
Sign in to ChatGPT web or desktop, open Plugins and select Add. Choose Upload plugin archive for the GWC Bridge ZIP, or Add custom MCP server on the same Plugins page. If Web offers Open in desktop app, use it to complete setup there.
- ChatGPT web
https://chatgpt.com
- 3
Add the GWC Bridge server
With Upload plugin archive, the ZIP already contains the GWC Bridge MCP Server URL. With Add custom MCP server, name it GWC Bridge, set Connection to Server URL and paste the exact MCP address. Never paste a private client credential.
- MCP Server URL
https://mcp.gwc-corp.com/mcp
- 4
Keep automatic OAuth and PKCE
Both routes use portable OAuth. With Add custom MCP server, select OAuth and leave Advanced OAuth Client ID and Client Secret blank to discover the public Client ID Metadata Document. Upload plugin archive already includes OAuth/CIMD. GWC uses PKCE S256, not a pasted secret.
- 5
Authorize and enable the plugin
With Upload plugin archive, open GWC Bridge under Plugins and Connect, or follow Open in desktop app if ChatGPT web offers that. With Add custom MCP server, review the warning, Create as a plugin and Connect GWC Bridge. Sign in to GWC with the account used on your computer, confirm Connected and Try in chat.
- 6
Verify read-only access
Ask the plugin for an allowed computer and shared-folder list first. Keep independent ChatGPT and PC confirmations for file changes and commands.
- Read-only test request
Use GWC Bridge to show which of my computers and shared folders are available. Do not change files or run commands.
After Connected: verify read-only access
Connected verifies OAuth, not that your computer or shared folder can be reached. Send this request to your AI chat:
- Read-only test prompt
Use GWC Bridge. First run who_am_i, then list_folders. Show my GWC account, my intended computer online, and the test folder I shared with its root ID. Do not read or change files, run commands, or start tasks.
Success: who_am_i shows your GWC account, and list_folders responds from the intended online computer with your shared folder. If not, check Bridge and Selected folders on your computer; OAuth alone is not a working connection.
To change access, open GWC Bridge in GWC Studio on your computer, or run GWC: GWC Bridge (command gwc.openBridge) in the VS Code Command Palette. GWC for Web only shows connected computers.
Claude
For Claude, upload the GWC Bridge plugin ZIP or add a custom MCP connector; choose one route.
Claude custom remote connectors are offered on eligible free and paid Claude plans. Organization connectors require an authorized Owner or role.
Claude: Download the ZIP, then Customize > Plugins > Add > Upload plugin. Open GWC Bridge > Connectors > Connect and sign in to GWC if asked. Or use the custom MCP setup below; choose one route.
Claude — Full setup and troubleshooting guide
Claude — Detailed manual setup guideSetup overview
- 1
Prepare your computer for GWC Bridge
Use an active Connect Pass with GWC Studio or GWC for VS Code running on the intended computer, signed in to the same GWC account. Share your project folders.
- 2
Choose a Claude setup method
Plugin ZIP: Customize > Plugins > Add > Upload plugin. Choose the GWC Bridge ZIP and Upload, then open GWC Bridge > Connectors > Connect. Or use Customize > Connectors > Yours > Add > Add custom connector without a ZIP. Choose one method only.
- Claude web
https://claude.ai
- 3
Connect the built-in or custom server
For custom MCP, name it GWC Bridge, paste the MCP Server URL and leave OAuth Client ID and Client Secret empty. For an uploaded ZIP, its connector is prefilled; verify the URL, then choose Continue.
- MCP Server URL
https://mcp.gwc-corp.com/mcp
- 4
Use Claude's published identity
Keep Authentication as Sign in now and OAuth client as Use Claude's published identity (Recommended). Do not register a new client or enter request headers. GWC handles automatic CIMD discovery and PKCE.
- 5
Authorize the chosen Claude connection
Choose Continue and Add for your connector, then finish GWC sign-in if prompted using the same account as your running computer. Existing authorization may be reused. Wait for the tools, open a new chat and enable GWC Bridge if needed.
- 6
Verify read-only access
Check the actual tool result for authorized computers and shared folders before allowing file changes or commands.
- Read-only test request
Use GWC Bridge to show which of my computers and shared folders are available. Do not change files or run commands.
After Connected: verify read-only access
Connected verifies OAuth, not that your computer or shared folder can be reached. Send this request to your AI chat:
- Read-only test prompt
Use GWC Bridge. First run who_am_i, then list_folders. Show my GWC account, my intended computer online, and the test folder I shared with its root ID. Do not read or change files, run commands, or start tasks.
Success: who_am_i shows your GWC account, and list_folders responds from the intended online computer with your shared folder. If not, check Bridge and Selected folders on your computer; OAuth alone is not a working connection.
To change access, open GWC Bridge in GWC Studio on your computer, or run GWC: GWC Bridge (command gwc.openBridge) in the VS Code Command Palette. GWC for Web only shows connected computers.
Gemini
Set up a Custom MCP Server data store in Gemini. This route is not a consumer Gemini or Gemini CLI setup.
You need a Google Cloud project, an Organization Policy Administrator to allow custom MCP data stores, and a Discovery Engine Editor to create the data store. Check VPC Service Controls and connector egress policies where enforced.
Gemini — Detailed manual setup guideSetup overview
- 1
Prepare your GWC computer and Google Cloud roles
Sign in to GWC Studio or GWC for VS Code on the online PC, maintain an active Connect Pass, and confirm the Google Cloud roles and project allow Custom MCP Server data stores.
- 2
Allow custom MCP data stores
In Organization Policies set Disable custom MCP server connector for Gemini Enterprise to Off for the project. If restricted, allow the custom_mcp data source and the GWC egress domains.
- Data source identifier
custom_mcp- MCP egress domain
mcp.gwc-corp.com- OAuth egress domain
api.gwc-corp.com
- 3
Create a Gemini data store
Open Gemini → Data stores → Create data store. Find Custom MCP Server, select Add MCP server and choose OAuth 2.0 authentication.
- 4
Enter the exact server and OAuth endpoints
Copy each field into the matching Gemini form. Keep Authorization URL Parameters blank.
- MCP Server URL
https://mcp.gwc-corp.com/mcp- Authorization URL
https://hk.gwc-corp.com/oauth/authorize- Token URL
https://hk.gwc-corp.com/oauth/token- Issuer
https://hk.gwc-corp.com
- 5
Configure the public OAuth client
Use Authorization Code with Enable PKCE Support On (S256), Client Secret none (a required form placeholder, not a real secret), and Use HTTP Basic Auth Off if shown. Enter the exact public client and scopes below. The callback shown is Google's hosted redirect.
- Client ID
gwc-google-gemini-v1- Client Secret placeholder
none- Scopes
files:read files:write commands:run- OAuth redirect URL
https://vertexaisearch.cloud.google.com/oauth-redirect
- 6
Verify Auth and activate the data store
Select Verify Auth, sign in and consent to GWC, choose Continue, select the Multi-region and data connector name, then Create. Wait until the data store reports Active.
- 7
Enable actions and check safely
Use Actions → Reload custom actions, select only needed GWC Bridge actions, then Enable actions and attach the data store to the intended Gemini app. Test read-only first.
- Read-only test request
Use GWC Bridge to show which of my computers and shared folders are available. Do not change files or run commands.
Grok
Connect GWC Bridge at grok.com.
Use the supported Grok connector flow and an active Connect Pass. GWC handles the public OAuth client identity.
You can read these steps, but manual setup is not currently available for this AI app.
Grok — Detailed manual setup guideSetup overview
- 1
Prepare your computer
Run GWC Studio or GWC for VS Code, sign in to the same GWC account, and review the shared folders before approving.
- 2
Add a Grok custom connector
At grok.com choose Connectors > New Connector > Custom. Name it GWC Bridge.
- MCP Server URL
https://mcp.gwc-corp.com/mcp
- 3
Use automatic OAuth with PKCE
GWC handles the client ID. Do not enter an API key, bearer token or client secret.
- 4
Sign in and authorize
Use the same GWC account and approve only if you accept every shared folder and every permission the server supports. You cannot select a subset during sign-in.
- 5
Check the connection
Ask Grok for ping and list_folders. Confirm the actual computer and folder labels before file operations.
- Read-only test request
Use GWC Bridge to show which of my computers and shared folders are available. Do not change files or run commands.
Muse (Meta)
Connect Meta's Muse to GWC Bridge. Muse runs in Meta's cloud; Meta says connector information is used to improve AI at Meta.
An active Connect Pass and an online GWC Studio or GWC for VS Code computer are required. Review sharing before approval.
Muse (Meta) — Detailed manual setup guideSetup overview
- 1
Prepare your computer
Sign in to GWC Studio or GWC for VS Code and review every shared folder. One GWC approval grants every shared folder and all server-supported permissions.
- 2
Add a Muse MCP connector
Name it GWC Bridge and enter the server address. OAuth with PKCE needs no API key or bearer token.
- MCP Server URL
https://mcp.gwc-corp.com/mcp
- 3
Enter the existing Muse client ID
Use the public ID already registered by GWC. No client secret or new registration. The registered callback is https://agent.meta.ai/api/hatch/oauth/callback.
- Client ID
gwc-meta-muse-v1
- 4
Sign in and tap Connect
Use the same GWC account; review the full access and tap Connect once on the GWC page. Meta's connector data-use notice also applies.
- 5
Check the connection
Run ping then list_folders. Do not change files just to check the connection.
- Read-only test request
Use GWC Bridge to show which of my computers and shared folders are available. Do not change files or run commands.
GWC Bridge
Give AI access to the computer you choose.
Start with GWC Studio or GWC for VS Code on that computer.
See GWC apps