# OpenWork MCP Gateway [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/different-ai/openwork  
**GitHub Stars:** 24498  
**Views:** 9  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/openwork-mcp-gateway

## Description
Your OpenWork org's skills, plugins, workflows, and connections through one OAuth MCP URL.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "openwork-mcp-gateway": {
    "url": "https://api.openworklabs.com/mcp/agent"
  }
}
```

## Documentation

## What OpenWork MCP Gateway does

OpenWork MCP Gateway gives compatible AI agents access to capabilities managed through OpenWork. Those capabilities can include assigned skills, plugins, MCP connections, Google Workspace functions, and Microsoft 365 functions. An agent can use the gateway instead of receiving separate configuration for every shared service or MCP connection.

The gateway is particularly useful when an organization wants to publish capabilities centrally and make them available to selected users or teams. OpenWork Den can manage organization membership, teams, access rules, published skills, plugins, and shared or per-user connections. The gateway then exposes the capabilities assigned to the authenticated user.

## How it works

The hosted MCP endpoint is available at:

```text
https://api.openworklabs.com/mcp/agent
```

Clients connect to this remote endpoint using MCP over HTTP. Authentication uses OAuth: after the MCP is added, the client opens a browser for sign-in and organization selection. The agent’s available capabilities depend on the resulting OpenWork account and organization permissions.

Four MCP tools form the main interface:

- `search_capabilities` discovers available capabilities.
- `execute_capability` runs a selected capability.
- `list_skills` returns the skills available to the user.
- `get_skill` reads an individual `SKILL.md` file directly.

The desktop application is optional for this use case. Agents can use the remote gateway directly, while teams can use OpenWork’s control plane to administer shared access and published capabilities.

## Setup and configuration

Add the remote URL to an MCP-compatible client. For Codex, the documented command is:

```bash
codex mcp add openwork --url https://api.openworklabs.com/mcp/agent
```

Claude Code can be configured with:

```bash
claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent
```

OpenCode uses a remote MCP entry with OAuth enabled:

```json
{
  "mcp": {
    "openwork": {
      "type": "remote",
      "enabled": true,
      "url": "https://api.openworklabs.com/mcp/agent",
      "oauth": {}
    }
  }
}
```

Other MCP clients can use the same endpoint when they support remote MCP connections and OAuth authentication. After setup, complete the browser sign-in flow and choose the relevant OpenWork organization.

## Limitations and notes

Access is governed by OpenWork organization assignments and permissions, so adding the endpoint does not automatically grant every available capability. The gateway depends on the hosted OpenWork service and the connected services made available through the organization.

The repository uses separate licensing for its components. Code under `ee/`, which includes the organization control plane and MCP gateway, is covered by the OpenWork EE License. Production use has subscription terms, with stated exceptions for organizations of up to five users, evaluation periods, and development or testing.

_Full upstream README: https://allmcps.com/mcp/openwork-mcp-gateway/readme_