2026-09-02 01:05:41 +08:00
commit 04bac1f6e2
2200 changed files with 489415 additions and 0 deletions
@@ -0,0 +1,92 @@
---
title: "OpenWork Connect as an Agent Plugin"
sidebarTitle: "Agent Plugins"
description: "Install OpenWork Connect as one portable Agent Plugin, or import compatible Agent Plugins into your organization's Library."
---
[Agent Plugins](https://agent-plugins.org/) is an open package format that can
ship Agent Skills and MCP configuration together. OpenWork publishes a
standards-compliant package for OpenWork Connect at
[`integrations/agent-plugins/openwork-connect`](https://github.com/different-ai/openwork/tree/dev/integrations/agent-plugins/openwork-connect).
## What the OpenWork package installs
The package contains:
- `plugin.json`, targeting the published Agent Plugins 1.0.0 schema for broad
  client compatibility;
- `mcp.json`, pointing at the OpenWork Connect Streamable HTTP endpoint;
- an `openwork-connect` skill that teaches the agent to search for an exact
  organizational capability before executing it.
Install or copy the complete package directory using your client's Agent
Plugins workflow. The standard does not define a registry or one universal
installation command, so the last installation step depends on the client.
The package does not contain credentials or an `Authorization` header. Your
MCP client discovers OpenWork OAuth from the endpoint, opens browser sign-in,
and scopes the resulting authorization grant to the selected organization.
The Agent Plugin selects the `streamable-http` transport; it does not pin a
wire-protocol revision. OpenWork Connect negotiates stateless MCP 2026-07-28
with current clients while retaining its MCP 2025-11-25 compatibility path.
Existing clients can therefore continue using the same endpoint as they move
to the current MCP protocol.
## What this enables for an organization
An administrator can manage skills, shared MCP connections, and connected
services once in OpenWork. Members can then install one portable OpenWork
package in a compatible agent and receive only the capabilities granted to
them through their organization, teams, and individual access rules.
This separates distribution from access control:
1. the Agent Plugin tells the client how to reach OpenWork;
2. OpenWork determines what the signed-in member can discover;
3. `search_capabilities` returns relevant authorized capabilities;
4. `execute_capability` runs the selected capability or returns an actionable
   connection or permission state.
The result is one reusable organization capability layer across compatible
agents instead of a separate MCP and skill configuration for every client,
teammate, and machine.
## Import Agent Plugins into OpenWork Library
OpenWork's GitHub plugin importer recognizes the published Agent Plugins 1.0.0
schema and the schema-identical 1.1.0 working draft at a repository root or
subdirectory. It validates `plugin.json`, requires `mcp.json` to target the
same schema version, discovers only immediate `skills/<name>/SKILL.md`
entrypoints, and reads the package-root `mcp.json`. Existing 1.0.0 packages
remain valid when 1.1.0 packages are imported.
The Den import path currently supports:
- standards-compliant Agent Skills whose instructions are contained in
  `SKILL.md`;
- remote `streamable-http` MCP servers;
- legacy remote `sse` entries supported by the existing connection runtime;
- independent failure reporting, so one invalid skill or server does not hide
  valid siblings;
- Agent Plugin format and schema-version provenance on the imported Plugin.
The Den import path reports but does not install:
- local `stdio` servers, because they require a desktop execution and trust
  policy;
- remote entries with static headers, because OpenWork does not yet persist or
  forward arbitrary package headers;
- additional scripts or assets referenced by a skill. The `SKILL.md`
  entrypoint is imported and the omitted assets are reported.
These limits are explicit in the import preview so an administrator cannot
mistake a partial package for a fully configured organizational Plugin.
## Authentication
Agent Plugins does not define portable OAuth fields. Do not add an OAuth object,
bearer token, or secret header to the package. OpenWork Connect uses MCP
protected-resource discovery, browser authorization, PKCE, and the client's
credential store as described in the
[OpenWork Connect reference](/cloud/run-in-the-cloud/cloud-mcp).
@@ -0,0 +1,67 @@
---
title: "OpenWork MCP for ChatGPT"
sidebarTitle: "ChatGPT"
description: "ChatGPT MCP setup for OpenWork Connect, so ChatGPT Desktop can use your org's shared OpenWork capabilities through OAuth."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables ChatGPT 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 ChatGPT 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).
## Setup
1. Open ChatGPT `Settings > MCP servers`
   ([open settings](https://chatgpt.com/#settings/Connectors)).
2. Paste the server URL:
   ```text
   https://api.openworklabs.com/mcp/agent
   ```
3. Start OAuth from ChatGPT's connection prompt, sign in to OpenWork, and pick
   the organization ChatGPT should use.
## Switch organizations
Open ChatGPT `Settings > MCP servers`, disconnect or clear the `OpenWork`
server's stored auth, then connect again and choose the organization you want.
<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. ChatGPT 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?"
- "Search my org's capabilities for calendar tools, then list tomorrow's events."
- "Create a skill that writes weekly status reports and share it with my whole organization."
- "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).
@@ -0,0 +1,69 @@
---
title: "OpenWork MCP for Claude Code"
sidebarTitle: "Claude Code"
description: "Claude Code MCP setup for OpenWork Connect, with OAuth access to your org's Gmail, Calendar, Drive, shared MCP connections, skills, and Cloud resources."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables Claude Code 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 Code 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).
## Setup
1. Add OpenWork Connect as a remote HTTP MCP server:
   ```sh
   claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent
   ```
   Add `-s user` to make it available in every project.
2. Open Claude Code and run `/mcp`.
3. Select `openwork`, then follow the browser sign-in and choose your
   organization.
## Switch organizations
Run `/mcp` inside Claude Code, select `openwork`, then clear or
re-authenticate the connection. The next browser sign-in lets you pick a new
organization.
<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 Code 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?"
- "Search my org's capabilities for calendar tools, then list tomorrow's events."
- "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).
@@ -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).
@@ -0,0 +1,76 @@
---
title: "OpenWork MCP for Codex"
sidebarTitle: "Codex"
description: "Codex MCP setup for OpenWork Connect, with OAuth access to your org's Gmail, Calendar, Drive, shared connections, skills, and Cloud resources."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables Codex 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 Codex 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).
## Setup
1. Add OpenWork Connect:
   ```sh
   codex mcp add openwork --url https://api.openworklabs.com/mcp/agent
   ```
2. Log in and finish the browser sign-in:
   ```sh
   codex mcp login openwork
   ```
In the Codex desktop app, open `codex://settings/connections` and paste the
server URL there instead.
## Switch organizations
Log out, then log in again and choose the organization you want:
```sh
codex mcp logout openwork
codex mcp login openwork
```
<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. Codex 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."
- "Search my org's capabilities for calendar tools, then list tomorrow's events."
- "Create a skill that writes weekly status reports and share it with my whole organization."
## 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).
- Connect from a remote environment with
  [OpenWork MCP on a remote machine](/cloud/run-in-the-cloud/connect-openwork-mcp-remote-machine).
@@ -0,0 +1,76 @@
---
title: "OpenWork MCP for Cursor"
sidebarTitle: "Cursor"
description: "Cursor MCP setup for OpenWork Connect on Cursor Desktop, Cursor Web, and Cursor Agents."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables Cursor 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 Cursor 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).
## Cursor Desktop
Add OpenWork as a remote MCP server in Cursor's MCP settings, paste the server
URL, and start OAuth from Cursor's connection prompt. Sign in to OpenWork and
pick the organization Cursor should use.
Cursor Desktop's OAuth callback is the private-use URI
`cursor://anysphere.cursor-mcp/oauth/callback`. OpenWork accepts exactly this
callback through an allowlist and enforces PKCE S256 for the client, so an
intercepted authorization code cannot be redeemed without the code verifier.
Other private-use callback schemes remain rejected: OpenWork otherwise accepts
HTTPS callbacks or HTTP loopback callbacks only.
## Cursor Web and Cursor Agents
Use Cursor Web or Cursor Agents where they ask for a remote MCP server URL.
Paste the server URL, start OAuth from Cursor's connection prompt, sign in to
OpenWork, and pick the organization Cursor should use.
Cursor Web and Cursor Agents use HTTPS OAuth callbacks, which OpenWork
accepts.
## 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 for Cursor Desktop, Cursor Web, and Cursor Agents. These
steps match OpenWork Connect's OAuth profile: HTTPS or HTTP loopback callbacks
plus Cursor Desktop's allowlisted private-use callback, PKCE S256, and dynamic
client registration fallback. Cursor 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."
- "Search my org's capabilities for calendar tools, then list tomorrow's events."
- "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).
@@ -0,0 +1,75 @@
---
title: "OpenWork MCP for Gemini CLI"
sidebarTitle: "Gemini CLI"
description: "Gemini CLI MCP setup for OpenWork Connect, with OAuth access to your org's Gmail, Calendar, Drive, shared connections, skills, and Cloud resources."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables Gemini CLI 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 Gemini CLI 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).
## Setup
1. Add OpenWork Connect as a remote HTTP MCP server:
   ```sh
   gemini mcp add --transport http openwork https://api.openworklabs.com/mcp/agent
   ```
2. Start Gemini CLI:
   ```sh
   gemini
   ```
3. Authenticate OpenWork inside Gemini:
   ```text
   /mcp auth openwork
   ```
4. Finish the browser sign-in and choose your organization.
## Switch organizations
Remove the stored MCP auth token for `openwork`, then run `/mcp auth openwork`
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. Gemini CLI 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."
- "Search my org's capabilities for calendar tools, then list tomorrow's events."
- "Create a skill that writes weekly status reports and share it with my whole organization."
## 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).
@@ -0,0 +1,84 @@
---
title: "OpenWork MCP for OpenCode"
sidebarTitle: "OpenCode"
description: "OpenCode MCP setup for OpenWork Connect, OpenWork's hosted MCP server for Gmail, Calendar, Drive, shared connections, skills, and Cloud resources."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables OpenCode 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 OpenCode 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).
## Setup
1. Add this MCP entry to your `opencode.json` file:
   ```json
   {
     "mcp": {
       "openwork": {
         "type": "remote",
         "enabled": true,
         "url": "https://api.openworklabs.com/mcp/agent",
         "oauth": {}
       }
     }
   }
   ```
2. Authenticate the server:
   ```sh
   opencode mcp auth openwork
   ```
3. Finish the browser sign-in, then choose the organization OpenCode should use.
If OpenCode runs on a remote machine or SSH host, follow
[Connect OpenWork MCP from a remote machine](/cloud/run-in-the-cloud/connect-openwork-mcp-remote-machine).
## Switch organizations
Log out, then authenticate again and pick the organization you want in the
browser:
```sh
opencode mcp logout openwork
opencode mcp auth openwork
```
<Note>
OpenCode is the verified OpenWork Connect client. Native remote MCP OAuth passed
end-to-end implementation testing.
</Note>
## What you can ask
- "Which OpenWork organization am I connected to?"
- "Add omar@example.com to my organization."
- "Create a skill that writes weekly status reports and share it with my whole organization."
- "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).
- Connect from an SSH host with
  [OpenWork MCP on a remote machine](/cloud/run-in-the-cloud/connect-openwork-mcp-remote-machine).
@@ -0,0 +1,83 @@
---
title: "OpenWork MCP for VS Code"
sidebarTitle: "VS Code"
description: "VS Code MCP setup for OpenWork Connect, with OAuth access to your org's Gmail, Calendar, Drive, shared connections, skills, and Cloud resources."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables VS Code 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 VS Code 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).
## Setup
Run this command:
```sh
code --add-mcp '{"name":"openwork","type":"http","url":"https://api.openworklabs.com/mcp/agent"}'
```
Then open the Command Palette and run `MCP: List Servers` > `openwork` >
`Start Server`. Follow the sign-in prompt and choose your organization.
## Manual setup
Open the Command Palette and run `MCP: Open User Configuration`, or edit
`.vscode/mcp.json` for one workspace:
```json
{
  "servers": {
    "openwork": {
      "type": "http",
      "url": "https://api.openworklabs.com/mcp/agent"
    }
  }
}
```
Then run `MCP: List Servers` > `openwork` > `Start Server`, and follow the
sign-in prompt.
## Switch organizations
Remove the stored MCP auth token for `openwork`, then start the server 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. VS Code 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?"
- "Assign Priya to the Sales team."
- "Search my org's capabilities for calendar tools, then list tomorrow's events."
- "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).
@@ -0,0 +1,75 @@
---
title: "OpenWork MCP for Windsurf"
sidebarTitle: "Windsurf"
description: "Windsurf MCP setup for OpenWork Connect through mcp-remote and OAuth access to your org's shared capabilities."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables Windsurf 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 Windsurf 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).
## Setup
1. Open Windsurf `Settings` > `Cascade` > `MCP Servers`.
2. Click `Manage MCP Servers`, then `View raw config`.
3. Add this to `~/.codeium/windsurf/mcp_config.json`:
   ```json
   {
     "mcpServers": {
       "openwork": {
         "command": "npx",
         "args": ["-y", "mcp-remote@latest", "https://api.openworklabs.com/mcp/agent"]
       }
     }
   }
   ```
`mcp-remote` handles the browser OAuth on an HTTP loopback callback, which
OpenWork accepts.
## Switch organizations
Remove the stored MCP auth token for `openwork`, then restart the server 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. Windsurf 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."
- "Create a skill that writes weekly status reports and share it with my whole organization."
- "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).
@@ -0,0 +1,72 @@
---
title: "OpenWork MCP for Zed"
sidebarTitle: "Zed"
description: "Zed MCP setup for OpenWork Connect through mcp-remote and OAuth access to your org's shared capabilities."
---
The OpenWork MCP server ([OpenWork Connect](/cloud/run-in-the-cloud/cloud-mcp))
enables Zed 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 Zed 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).
## Setup
Add this to Zed `settings.json`:
```json
{
  "context_servers": {
    "openwork": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://api.openworklabs.com/mcp/agent"],
      "env": {}
    }
  }
}
```
`mcp-remote` handles the browser OAuth on an HTTP loopback callback, which
OpenWork accepts.
## Switch organizations
Remove the stored MCP auth token for `openwork`, then restart the server 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. Zed 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?"
- "Assign Priya to the Sales team."
- "Search my org's capabilities for calendar tools, then list tomorrow's events."
- "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).