> ## 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 Cursor

> Cursor MCP setup for OpenWork Connect on Cursor Web and Agents, plus why Cursor Desktop OAuth is not currently supported.

The OpenWork MCP server ([OpenWork Connect](/docs/cloud/run-in-the-cloud/cloud-mcp))
enables Cursor Web and Cursor Agents 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 Cursor 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).

## 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 can use HTTPS OAuth callbacks, which OpenWork
accepts.

## Cursor Desktop is not currently supported

Cursor Desktop OAuth requires `cursor://anysphere.cursor-mcp/oauth/callback`, a
private-use scheme that OpenWork's MCP profile intentionally rejects. OpenWork
accepts HTTPS callbacks or HTTP loopback callbacks only.

Use Cursor Web/Agents, or use a verified client like
[OpenCode](/docs/model-context-protocol/opencode), until Cursor Desktop can use an
accepted callback type.

## 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 Web and Cursor Agents. These steps match
  OpenWork Connect's OAuth profile: HTTPS or HTTP loopback callbacks, PKCE S256,
  and dynamic client registration fallback. Cursor 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?"
* "Add [omar@example.com](mailto: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](/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).