源码快照 @ 2026-09-02 (source-only, 剔除非源码素材)

packages/docs/model-context-protocol/claude-desktop.mdx

@@ -0,0 +1,89 @@
+---
+title: "OpenWork MCP for Claude Desktop"
+sidebarTitle: "Claude Desktop"
+description: "Claude Desktop MCP setup for OpenWork Connect, using custom connectors or mcp-remote to reach your org's shared capabilities."
+---
+
+The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
+enables Claude Desktop to use the OpenWork capabilities your organization has
+made available to you: Gmail read/search, Calendar list/create, Drive
+search/read, Gmail draft creation, shared MCP connections such as Notion,
+Linear, Slack, Stripe, Exa, and Context7, shared skills, and OpenWork Cloud
+resources like skills, plugins, Collections, workers, members, roles, teams,
+and LLM providers. The server exposes only `search_capabilities` and
+`execute_capability`, so Claude Desktop searches what you can access and runs
+exact capability names instead of loading hundreds of tool definitions into
+context.
+
+## Server URL
+
+```text
+https://api.openworklabs.com/mcp/agent
+```
+
+OAuth sign-in uses your OpenWork account, and the organization you pick is
+pinned into the token. If you do not have an account, create a
+[free OpenWork account](https://app.openworklabs.com?mode=sign-up).
+
+## Connect
+
+1. Open Claude Desktop `Settings` > `Connectors`.
+
+2. Click `Add custom connector`.
+
+3. Name it `OpenWork` and set the URL to:
+
+   ```text
+   https://api.openworklabs.com/mcp/agent
+   ```
+
+4. Click `Connect`, then finish the browser sign-in and choose your
+   organization. Claude's connector OAuth uses an HTTPS callback, which
+   OpenWork accepts.
+
+## Fallback config
+
+For Claude Desktop builds without custom connectors, open `Settings` >
+`Developer` > `Edit Config` and add this to `claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "openwork": {
+      "command": "npx",
+      "args": ["-y", "mcp-remote@latest", "https://api.openworklabs.com/mcp/agent"]
+    }
+  }
+}
+```
+
+`mcp-remote` runs the OAuth locally on an HTTP loopback callback, which
+OpenWork accepts. Restart Claude Desktop after editing the config.
+
+## Switch organizations
+
+Remove the stored MCP auth token for `openwork`, then connect again and choose
+the organization you want during browser sign-in.
+
+<Note>
+This is a setup guide. These steps match OpenWork Connect's OAuth profile:
+HTTPS or HTTP loopback callbacks, PKCE S256, and dynamic client registration
+fallback. Claude Desktop is listed as setup only because native proof is not
+complete. See the
+[client support status](/cloud/run-in-the-cloud/cloud-mcp#client-support-status)
+table.
+</Note>
+
+## What you can ask
+
+- "Which OpenWork organization am I connected to?"
+- "Add omar@example.com to my organization."
+- "Assign Priya to the Sales team."
+- "Find the Q3 launch page in Notion and summarize it."
+
+## What's next
+
+- Read the [hub overview](/cloud/run-in-the-cloud/cloud-mcp) for OAuth, token,
+  server exposure, and troubleshooting details.
+- Publish Notion, Linear, Slack, and other shared tools with
+  [shared MCP connections](/cloud/share-with-your-team/shared-mcp-connections).