Skip to content

Connect GWC Bridge to Muse

Follow these steps to connect Muse to GWC Bridge.

1. Before you start

An active Connect Pass and a signed-in GWC Studio or GWC for VS Code on your computer are required.

One GWC approval covers all folders shared by computers on your GWC account and all permissions supported by the server. You cannot choose individual folders or permissions during sign-in. Limit sharing in GWC Studio or GWC for VS Code before approving.

Do not enter an API key, bearer token or client secret. GWC uses OAuth with PKCE.

2. Add the connector

  1. Open Muse (Meta's assistant) and add a custom MCP connector named GWC Bridge.
  2. Enter the MCP server URL and the existing public Client ID gwc-meta-muse-v1; leave the client secret empty. Do not register a new client.
  3. Muse uses the registered callback https://agent.meta.ai/api/hatch/oauth/callback. Do not change or guess the callback.

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

3. Sign in and approve

Muse runs in Meta's cloud. Meta's connector screen says information from a connector is used to improve AI at Meta.

  1. Sign in with the same GWC account used on your desktop computer.
  2. Check the full GWC Bridge access presented by GWC. Approve only if every currently shared folder and every server-supported permission is acceptable. This is not a read-only grant.
  3. Tap Connect once on the GWC page, then return to Muse.

4. Check the connection

Ask the assistant to run ping, then list_folders. Check the returned computer and folder names before requesting file work.

Use GWC Bridge to run list_devices, then ping and list_folders for your chosen computer. Return computer names and status from list_devices and folder labels from list_folders. Do not open, read or change files.

5. Troubleshooting

If the wrong GWC account appears, choose another account and repeat sign-in. If the callback or sign-in fails, start a fresh connection; do not reuse a code.

GWC Bridge · GWC apps