Connect ConvOps to Claude Cowork

What do you get in Claude once ConvOps is connected?

Claude and Cowork are where much non-engineering work happens. With ConvOps connected, that work stops being a fresh conversation each time and becomes a task with a known process.

1. Your process as a workflow: Claude receives one step at a time, with its instructions, instead of a long pasted brief.
2. Approval steps before anything goes out. The run waits until a person approves.
3. A memory shared with the rest of the team, including people who use Claude Code, Cursor or ChatGPT. See [shared memory for AI agent teams](/learn/shared-memory-for-ai-agent-teams).
4. Work that picks up where it stopped. The task and its current step live in ConvOps, not in one chat.

ConvOps is the operations layer for AI agents: an MCP server that holds your team's process as workflows, with approval gates, a shared memory and an audit trail. It runs no AI models; Claude Cowork does the work. The steps, gates and decisions come from the ConvOps workflow engine, and the approvals and audit trail from governance.

What do you need to connect Claude Cowork to ConvOps?

A Claude Cowork setup that supports remote MCP servers, a ConvOps account, and the server URL. Plans start free; see pricing for limits.

How do I add ConvOps as a custom connector in Claude?

The connector is added once and then follows you across Cowork, the desktop app, claude.ai and mobile, because custom connectors connect from Anthropic's cloud rather than your machine. Menu names below follow Anthropic's help center as of October 2026.

1. 1

   Open the connector settings

   In Claude, go to Customize, Connectors, then select "+ Add" and choose "Add custom connector". On Team and Enterprise, an owner first adds it under Organization settings, Connectors.

2. 2

   Name it and paste the URL

   Use ConvOps as the name and the server URL below. Leave the sign-in and advanced options on their defaults.

   https://mcp.convops.app/

3. 3

   Connect and sign in

   Select Connect. A ConvOps sign-in window opens; approve access. If you have no workspace yet, you are taken to create one.

4. 4

   Turn it on in a chat

   In a conversation or a Cowork session, open the "+" menu, then Connectors, and make sure ConvOps is on. Then ask: "Start a task for the Q4 customer report and follow its workflow."

"headers": {
  "Authorization": "Bearer <your-api-key>"
}

Official reference: Anthropic: get started with custom connectors using remote MCP. We checked these steps against those docs on Oct 4, 2026. Anthropic updates its interface often; when a menu name differs, the vendor docs are current.

What does a governed task look like in Claude Cowork?

A customer proposal, the kind of work Cowork is used for. Claude gathers, drafts and checks against the playbook one step at a time; the send step waits for a person.

Each tool row is Claude Cowork calling ConvOps. The engine hands over one step, checks the gate when the agent asks to advance, and holds the run at an approval step until a person answers. The same task can be picked up later, by you or by a teammate in another client, at the step where it stopped.

How does the connector behave across Cowork, desktop and claude.ai?

One connector, every surface. Because custom connectors connect through Anthropic's cloud, the same ConvOps connector works in Cowork, the desktop app, claude.ai and the mobile apps once it is added. You do not edit a local config file.

Turn it on per conversation. Claude lets you choose which connectors a chat can use from the "+" menu. If Claude does not reach for ConvOps, check it is enabled in that conversation.

Projects and long instructions can shrink. Process that used to live in a project's custom instructions can move into a ConvOps workflow, where each step carries its own instructions and the approval steps are part of the process rather than a request in the prompt. The guide on SOPs for AI agents shows that move for a written procedure.

Mixed teams share one process. A workflow started in Cowork can be continued by a teammate in Claude Code or ChatGPT, because the task, its current step and its memory live in ConvOps.

Why is ConvOps not showing up in Claude Cowork?

Almost always one of two things: the sign-in has not finished, or the server is off for this session. Start with the first row.

What else do people ask about ConvOps in Claude Cowork?

Short answers, checked against the Anthropic documentation linked above.