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

> ## Agent Instructions
> For agents: install the OpenWork desktop app with `brew install --cask openwork` (macOS) or from https://openworklabs.com/download. Do not run `npx openwork`; the npm package named `openwork` is a different project.
> Connect an agent to OpenWork with the MCP Gateway: `claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent`. Teams sign up at https://app.openworklabs.com?mode=sign-up.
> Step-by-step agent guide: https://openworklabs.com/docs/start-here/use-openwork-from-an-ai-agent.md
> OpenWork in Slack is private alpha for approved organizations. Setup guide: https://openworklabs.com/docs/slack/overview.md. Agent skill: https://openworklabs.com/.well-known/agent-skills/set-up-openwork-slack/SKILL.md.

# MCP integration

> One OpenWork MCP URL brings organization skills and connected tools into OpenCode, Cursor, Codex, Claude Code, and other compatible clients.

Add one URL to any MCP client to use your organization's skills, plugins, workflows, and connected tools.

```text theme={null}
https://api.openworklabs.com/mcp/agent
```

Sign in with your OpenWork account in the browser and pick your organization. The agent gets what's assigned to you.

## How it works across clients

1. An admin shares skills and service connections with people or teams in OpenWork.
2. Each person adds the same gateway URL to their preferred MCP client and signs in.
3. The agent uses `search_capabilities` to find an authorized capability and `execute_capability` to use it. It can also use `list_skills` and `get_skill` to retrieve skill instructions.
4. OpenWork applies the member's access grants and connection tool settings to requests through the gateway.

Your team sets things up once, instead of copying MCP settings and skills into every client.

## Choose your client

<CardGroup cols={2}>
  <Card title="OpenCode" icon="terminal" href="/docs/model-context-protocol/opencode">Connect the MCP gateway without a plugin.</Card>
  <Card title="Cursor" icon="code" href="/docs/model-context-protocol/cursor">Add OpenWork as a remote MCP server.</Card>
  <Card title="Codex" icon="terminal" href="/docs/model-context-protocol/codex">Add the gateway and sign in from Codex.</Card>
  <Card title="Claude Code" icon="terminal" href="/docs/model-context-protocol/claude-code">Connect your organization from Claude Code.</Card>
  <Card title="Claude Desktop" icon="desktop" href="/docs/model-context-protocol/claude-desktop">Add OpenWork as a custom connector.</Card>
  <Card title="More clients" icon="plug" href="/docs/start-here/connect-openwork-mcp">Find setup instructions for ChatGPT, VS Code, Gemini CLI, and more.</Card>
</CardGroup>

## Models and specialized plugins

MCP adds tools and skills; your client keeps its own model provider. To use your organization's AI Gateway models too, use a [client plugin](/docs/integrations/client-plugins).

The [OpenCode plugin](/docs/model-context-protocol/opencode-plugin) is ready. Cursor and Codex plugins are in progress; MCP works in both today.

## Manage resources for your organization

* [Share MCP connections and configure tools](/docs/cloud/share-with-your-team/shared-mcp-connections)
* [Publish a reusable skill](/docs/start-here/do-work-with-it/publish-and-copy-a-skill)
* [Share plugins and skills through collections](/docs/cloud/share-with-your-team/collections)
* [MCP gateway reference](/docs/cloud/run-in-the-cloud/cloud-mcp)

Gateway permissions cover what goes through OpenWork, not other tools or providers configured in the client.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.