cursor · mcp setup

Connect ConvOps to Cursor

Add ConvOps to ~/.cursor/mcp.json (or .cursor/mcp.json in a project) with the URL https://mcp.convops.app/, then sign in from the Customize page when Cursor connects. Cursor's agent gains ConvOps tools: tasks with workflows handed over one step at a time, engine-checked gates, approvals and a shared memory.

Cursor · mcp.jsonadding

~/.cursor/mcp.json

  • convops · signed in
  • tools enabled for Agent
tasksworkflowsgatesmemoryroutesschedules

example · the client's screens vary by version

server url
https://mcp.convops.app/
add it with
mcp.json entry
config lives in
~/.cursor/mcp.json or .cursor/mcp.json
sign-in
OAuth on first connect
01what you get

What do you get in Cursor once ConvOps is connected?

Cursor's agent edits code well. ConvOps adds the part that rules files cannot hold: a process with state, checks and approvals that persists across chats and teammates.

  1. Workflows the agent walks step by step, with the current step's instructions only.
  2. Gates the engine evaluates; an unmet one is returned to the agent with the reason.
  3. Approval gates that hold merge or release until an explicit approval is given.
  4. Shared memory and routes, so the agent knows where things live without a long rule file.

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. Cursor does the work. The steps, gates and decisions come from the ConvOps workflow engine, and the approvals and audit trail from governance.

02what you need

What do you need to connect Cursor to ConvOps?

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

You need Detail
CursorA version with remote MCP (Streamable HTTP).
A ConvOps accountThe Free plan works. Sign up at my.convops.app; a first sign-in without a workspace takes you to create one.
Server URLhttps://mcp.convops.app/
03setup steps

How do I add the ConvOps MCP server to Cursor?

Cursor reads MCP servers from a JSON file. Use the global file for yourself, or the project file to share the setup with the repository.

  1. 1

    Add ConvOps to mcp.json

    Create the file if it does not exist. If it does, add the convops entry inside mcpServers.

    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "convops": { "url": "https://mcp.convops.app/" }
      }
    }
  2. 2

    Sign in

    Open Customize in Cursor's sidebar, where MCP servers are managed, and find convops. Cursor supports OAuth for Streamable HTTP servers: start the sign-in there, your browser opens the ConvOps sign-in, and you approve access.

  3. 3

    Check the tools

    ConvOps should be enabled with its tools listed. Cursor's agent uses listed tools when relevant, under your run-mode settings.

  4. 4

    Start a task from the agent

    In Agent, ask: "Use ConvOps to start a feature task for CSV export and follow its workflow."

Prefer an API key?

To use an API key instead of OAuth, create one in the ConvOps app under Settings, API Keys and add it as a header. Keep a file with a key out of version control.

~/.cursor/mcp.json
{
  "mcpServers": {
    "convops": {
      "url": "https://mcp.convops.app/",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

Official reference: Cursor: Model Context Protocol, Cursor: rules. We checked these steps against those docs on . Anysphere updates its interface often; when a menu name differs, the vendor docs are current.

04in use

What does a governed task look like in Cursor?

A small feature. The plan step needs your OK before the agent writes code, so a wrong direction costs one message, not an afternoon.

example · Cursor · Agentconvops

new session

Use ConvOps. Add CSV export to the invoices table.
tasks_create · Feature attached · step 1 of 4
Plan: server-side stream, reuse the filters, button in the toolbar. OK to build?
Yes, cap it at 50k rows. Approved.
workflow_advance · approved · → build and test
Built with a 50k cap and a test for the limit.
example · Featurerunning
  1. Plannot handed over yet
  2. Plan approvalapproval
  3. Build and testnot handed over yet
  4. Open the PRnot handed over yet

example

Each tool row is Cursor 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.

05Cursor notes

Should the process live in Cursor rules or in ConvOps?

Rules for the code, workflows for the process. Cursor reads project rules from .cursor/rules and also supports AGENTS.md. Keep those for conventions and architecture. A process with ordered steps, checks and approvals fits ConvOps better, because the agent gets one step at a time and the state survives the chat. The glossary entry on agent instruction files draws the line.

Global or project file. ~/.cursor/mcp.json applies to every project you open. .cursor/mcp.json in the repository shares the server with the team; each person signs in with their own ConvOps account.

Run mode still applies. Per Cursor, it asks for approval before using MCP tools by default, following the same run modes as terminal commands. That is Cursor's control. ConvOps approval gates are separate: they are part of the workflow and recorded.

Planning tools fit next to it. Claude Task Master, for example, runs as an MCP server in Cursor and turns a PRD into a task list; ConvOps then governs how each task is done. See the Task Master comparison.

06troubleshooting

Why is ConvOps not showing up in Cursor?

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
ConvOps shows an error in CustomizeCheck the JSON is valid and the URL is exactly https://mcp.convops.app/ , then toggle the server off and on.
Login prompt never appearsRemove the server, save, add it back, and start the login from Customize.
Agent ignores the toolsAsk in Agent mode and name ConvOps in the request. Check the server is enabled.
Teammates cannot see itMove the entry to .cursor/mcp.json in the repository and commit it.
07questions

What else do people ask about ConvOps in Cursor?

Short answers, checked against the Anysphere documentation linked above.

Should I put ConvOps in the global or project mcp.json?

Global (~/.cursor/mcp.json) if it is just you. Project (.cursor/mcp.json) if the team should get ConvOps on clone. Everyone signs in with their own account either way, so the audit trail shows who did each step and nobody shares a token through the repository.

Do I still need Cursor rules?

Yes, for codebase conventions. Move ordered processes, checks and approvals into ConvOps workflows, where they have state and an audit trail. Rules tell Cursor how the code is written; a ConvOps workflow tells it which step comes next and holds that step until a gate's condition is met.

Can a Cursor user and a Claude Code user share a workflow?

Yes. Workflows and tasks live in the ConvOps workspace, so any connected client works the same process. A developer can start a bug fix in Cursor and a teammate can review and finish it from Claude Code, with the same step instructions, the same gates and one record of who did what.

Does ConvOps read my code?

No. Cursor works on your code. ConvOps only receives the tool calls the agent makes, such as a step result or a note to remember. Your repository stays where it is and is never uploaded to ConvOps; the step instructions tell Cursor what to do with it.

Can Cursor create a new ConvOps workflow?

Yes. Describe the process to Cursor in plain language, for example how your team runs an incident review, and it creates the workflow in ConvOps with steps, gates and decisions. The workflow is then available to every client in the workspace, and you change it the same way, by asking.