> ## Documentation Index
> Fetch the complete documentation index at: https://openworklabs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenWork MCP for VS Code

> 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](/docs/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, marketplaces, 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 theme={null}
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 theme={null}
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 theme={null}
{
  "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](/docs/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](/docs/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](/docs/cloud/share-with-your-team/shared-mcp-connections).
