Claude Cowork

Connect OpenQuok MCP to Claude Cowork via custom connectors or managedMcpServers organization settings.

2 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Prerequisites

Access to Claude Cowork organization settings (admin or connector manager).
An OpenQuok programmatic token (opo_) scoped to the workspace whose channels agents should manage.

Overview

Claude Cowork registers remote MCP servers at the organization level — either through the Custom connectors UI or a managedMcpServers JSON block in org settings. OpenQuok uses streamable HTTP transport; server name should be openquok.

Setup

Generate your token

In the OpenQuok app, open Account → Settings → Developers → Access. Create an OAuth app if prompted, then generate an opo_… token.

Generate programmatic token

Add the connector JSON

Paste one of the following arrays into Custom connectors or managedMcpServers (exact field name depends on your Cowork admin console):

[
  {
    "name": "openquok",
    "url": "https://api.openquok.com/mcp",
    "transport": "http",
    "headers": {
      "Authorization": "Bearer opo_your_programmatic_token"
    }
  }
]

[
  {
    "name": "openquok",
    "url": "https://api.openquok.com/mcp/opo_your_programmatic_token",
    "transport": "http"
  }
]

Save and propagate

Save organization settings. Cowork members may need to start a new session before openquok tools appear.

Verify

In a Cowork chat, ask:

List my connected social media accounts

The agent should call integrationList for the workspace tied to the token.

Workspace scope

Each opo_ token is bound to one OpenQuok workspace. Use separate tokens or connectors if different teams need isolated channel lists.

Self-hosted API

Replace https://api.openquok.com with your BACKEND_DOMAIN_URL origin.

Claude Code

Terminal claude mcp add setup

MCP clients overview

All supported MCP client guides

MCP introduction

Endpoints and authentication

Tools reference

v1 tool schemas