1 Prepare your Agent

Install the local Agent and approve the device in BrowzWork. The Default Workspace, Workspace Access, and background connection are configured automatically.

2 Create the app

In ChatGPT web, enable Developer mode. On Business, admins/owners create custom apps; on Enterprise/Edu, authorized developers can also create them after RBAC access is granted. Use Settings → Apps → Create or Workspace settings → Apps → Create as available, name the app BrowzWork, and enter the MCP endpoint below.

3 Authenticate and scan tools

Choose OAuth authentication. If ChatGPT exposes a custom OAuth client field, use the public client ID below and no client secret. Complete BrowzWork sign-in, then click Scan Tools.

Keep the server-discovered OAuth endpoints, MCP resource, and scopes unchanged. Do not paste any BrowzWork password or token into the app configuration.

4 Create and test

After the tool scan succeeds, click Create. Start a new chat, enable or @mention BrowzWork, then ask for device_list, select your device and Workspace, open a session, and read a harmless test file.

Write and command tools follow the locally granted Access Scope and Agent safety policy.

1 Prepare the Agent

Install the Agent and approve the device in BrowzWork. The Default Workspace, Workspace Access, and background connection are configured automatically.

2 Add a custom connector

For individual Free/Pro/Max accounts, open Customize → Connectors → + Add → Add custom connector. For Team, an Owner or Primary Owner uses Organization settings → Connectors → Add → Custom → Web; Enterprise also permits authorized custom roles with connector-management access. Name it BrowzWork and enter this server URL.

3 Choose OAuth

Select Sign in now and Use your own OAuth client. Enter this public client ID and leave the secret blank.

Keep the discovered endpoints and mcp:tools scope. Do not choose Claude's published identity or automatic registration for this server.

4 Connect and test

Finish adding the connector and complete BrowzWork sign-in. Then enable BrowzWork in a Claude conversation and test device list, selection, session open, and a harmless file read before edits or commands.

If OAuth sign-in cannot return to Claude, do not change BrowzWork endpoints manually; contact support with the error shown by Claude.

1 Prepare the Agent

Install the Agent and approve the device in BrowzWork. The Default Workspace, Workspace Access, and background connection are configured automatically.

2 Add the custom MCP connector

Open grok.com/connectors, choose New Connector → Custom, and enter this public MCP server URL.

3 Complete authentication

Let Grok discover the server authentication and complete BrowzWork sign-in. If Grok exposes advanced OAuth client fields, use the dedicated public client ID below with no client secret.

Do not manually enter authorization or token endpoints unless Grok explicitly asks for them; use the server-discovered metadata.

4 Connect and test

Finish the connector flow and complete BrowzWork sign-in. In a Grok conversation, enable BrowzWork and test device_list, device selection, session open, and a harmless file read before editing or running commands.

If OAuth sign-in fails, keep the server URL unchanged and use the error shown by Grok for troubleshooting.

1 Prepare the Agent

Confirm the device is paired and online. In Local Settings, explicitly update account access for the intended Workspace so the Web MCP bindings, including Cursor, and the DSH Harness MCP binding are present.

2 Add the remote MCP server

In Cursor Web or Cloud Agents, open the MCP menu. Team administrators can also use Dashboard → Plugins & MCPs for a shared server. Add a custom HTTP server named BrowzWork with this URL.

3 Authenticate

Configure static OAuth with the client ID below, no client secret, and scopes openid mcp:tools offline_access. Complete sign-in with your BrowzWork account. Use this server configuration where Cursor accepts MCP JSON:

{
  "mcpServers": {
    "BrowzWork": {
      "url": "https://mcp.browz.work/mcp",
      "auth": {
        "CLIENT_ID": "browzwork-cursor",
        "scopes": ["openid", "mcp:tools", "offline_access"]
      }
    }
  }
}

The registered Web callback is https://www.cursor.com/agents/mcp/oauth/callback. Do not use a Desktop localhost callback, a client secret, SSE, or mcp-remote for this Web setup.

If your Cursor form only supports dynamic registration and cannot preserve the static client ID, that form is not yet verified. Do not substitute another channel's client ID. Cursor static OAuth instructions ↗

4 Verify the managed path

In a new Cursor Web agent, list devices, select the intended device and Workspace, open a session, list the Workspace root, and read a harmless test file. Then verify one bounded write only if the local Access Scope permits it.

OAuth success alone is not a full gate pass; the real Cursor callback, token claim, tool discovery, and one remote file operation must all be recorded.

1 Prepare the Agent

Install the BrowzWork Agent on each computer you want to use. Confirm that the device is online, add the required Workspace in Local Settings, and leave remote access enabled.

2 Install the plugin

Download browzwork-dsh-bundle-0.1.0-alpha.7.tgz. Its SHA-256 is b59e1305881c8eef4a0fabe7242ad04d9b2f13efcc9d6e7bbb8936c0731a010f. Close DSH Desktop, then install it with the official DSH plugin manager and restart DSH Desktop completely.

Requires Agent 0.1.17. The DSH Desktop plugin remains a development prerelease. Execution-context history and hidden healthy status-sync rows on stock Desktop 0.2.0-rc.2 also require the reviewed core SDK compatibility update; plugin installation alone does not apply it. Use the official plugin manager for the plugin package.

3 Sign in and select your device

Open the BrowzWork sidebar in DSH Desktop and complete BrowzWork sign-in. Select your device and an added Workspace. The Device Owner can use all Workspaces added to the device through browzwork-dsh; no separate Workspace authorization is required. Use Local Settings ↗ to add or remove folders.

If the sign-in page asks you to return and refresh, use the BrowzWork sidebar's Refresh action. If it is not yet visible, close and reopen the BrowzWork sidebar; a full DSH restart is the recovery path for this prerelease.

4 Select and verify

Select a device and one of its added Workspaces, then test device_list, workspace_list, session_open, fs_list, and a harmless fs_read.

The plugin remembers the selected device and Workspace by their visible names. New conversations silently revalidate the saved choice and reuse a valid managed session; expired sessions or offline devices return a specific error code and recovery message.