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.
- Your process as a workflow: Claude receives one step at a time, with its instructions, instead of a long pasted brief.
- Approval gates before anything goes out: the step holds until an explicit approval is given, recorded with the account that gave it.
- 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).
- 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. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host 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.
| You need | Detail |
|---|---|
| A Claude plan | Custom connectors are available on Free, Pro, Max, Team and Enterprise. Free users are limited to one custom connector (per Anthropic). |
| Team or Enterprise | An owner adds the connector for the organization first; members then connect it. |
| A ConvOps account | The Free plan works. Sign up at my.convops.app; a first sign-in without a workspace takes you to create one. |
| Server URL | https://mcp.convops.app/ |
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
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
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.
remote mcp server url https://mcp.convops.app/ - 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
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."
Prefer an API key?
Claude connectors use OAuth, so there is no API key to paste. If you need a key for scripts or another client, create it in the ConvOps app under Settings, API Keys and use it there.
"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 . 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 an explicit approval.
new session
- Gather contextnot handed over yet
- Draftnot handed over yet
- Reviewapproval
- Sendnot handed over yet
example
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 gate until an explicit approval is given, recorded with the account that gave it. 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 gates 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.
| Symptom | Fix |
|---|---|
| Sign-in fails right after Connect | Open the connector's advanced settings and choose "Register automatically". ConvOps supports dynamic client registration. |
| ConvOps is missing in a chat | Open "+", then Connectors, and switch ConvOps on for that conversation. |
| A second connector will not add on Free | Free plans allow one custom connector. Remove the other one or upgrade your Claude plan. |
| Members on Team cannot find it | An owner must add it under Organization settings, Connectors first; members then connect from Customize, Connectors. |
What else do people ask about ConvOps in Claude Cowork?
Short answers, checked against the Anthropic documentation linked above.
Does ConvOps work in Claude Cowork?
Yes. Anthropic lists custom connectors as available in Claude, Cowork and Claude Desktop. Add ConvOps once as a custom connector and turn it on in the Cowork session. From there Cowork can list your tasks, follow a workflow one step at a time, record results and read the team's shared memory, like any other client that connects.
Do I need Claude Pro to use ConvOps?
No. Per Anthropic, custom connectors are available on Free, Pro, Max, Team and Enterprise, with Free limited to one custom connector. ConvOps also has a Free plan, so you can connect Claude and run a first workflow without paying either vendor. Your ConvOps plan and your Claude plan are separate, and each is billed by its own vendor.
Is my Claude chat history sent to ConvOps?
No. ConvOps receives only the tool calls Claude makes: the task, the step result it reports, and what it asks to remember or recall. The rest of the conversation stays with Anthropic under your Claude settings. What ConvOps does store, the step results and memories, is visible to your workspace and recorded in the audit trail.
Can the same workflow run in Claude and in Claude Code?
Yes. Workflows live in your ConvOps workspace, not in a client. Any connected client can pick up the task at its current step, so you can draft a launch brief in Claude on the web and have Claude Code finish the technical steps, with one record of who did what across both.
Can ConvOps run Claude Cowork on a schedule?
Not Cowork itself. A ConvOps schedule creates tasks at a time and in the time zone you set, and an executor can start an isolated run with Claude Code or OpenCode to work them unattended. Cowork stays the attended path: open the session, turn the connector on, and pick up any task at its current step.