OpenWork Cloud exposes a hosted MCP server at https://api.openworklabs.com/mcp. Add it to an MCP client when you want agents to use your OpenWork Cloud organization, skills, plugins, marketplaces, workers, and other Cloud API resources through MCP tools. The server uses OAuth. Your MCP client opens a browser, you sign in to OpenWork Cloud, choose the organization to authorize, and the client stores the returned token.

MCP config

Add this server to your MCP config:

{
  "mcp": {
    "openwork-cloud": {
      "type": "remote",
      "enabled": true,
      "url": "https://api.openworklabs.com/mcp",
      "oauth": {}
    }
  }
}

If your client expects the server map directly, use just the server entry:

{
  "openwork-cloud": {
    "type": "remote",
    "enabled": true,
    "url": "https://api.openworklabs.com/mcp",
    "oauth": {}
  }
}

Authorize access

1. Save the MCP config in your client.
2. Start the client’s MCP auth flow for openwork-cloud.
3. Sign in at app.openworklabs.com when the browser opens.
4. Choose the OpenWork Cloud organization that should receive MCP access.
5. Return to your MCP client after authorization completes.

The token is scoped to the organization you select during OAuth. If you need to switch organizations, remove the stored MCP auth token in your client and run the auth flow again.

What the server exposes

The hosted MCP server exposes OpenWork Cloud API tools for normal product resources, including config objects, connectors, plugins, marketplaces, skill hubs, skills, workers, members, roles, teams, and LLM providers. It intentionally does not expose authentication internals, admin-only system routes, webhooks, API-key creation or deletion, or credential-returning endpoints.

Requirements

• An OpenWork Cloud account and organization.
• An MCP client that supports remote Streamable HTTP MCP servers.
• OAuth support in the MCP client, including browser-based authorization.

If your client does not support OAuth for remote MCP servers, it cannot connect to openwork-cloud yet.