Cursor and Linear: assign issues to Cursor, or bring Linear into the editor

Ways to use Cursor with Linear

From Cursor's and Linear's documentation, checked November 14, 2026. Cursor's Cloud Agents were formerly called Background Agents. Linear lists Cursor as a featured agent and as an AI client for its MCP server.

Set up the Cursor Linear integration and delegate issues

This is the setup in Cursor's docs. Only a Cursor admin can connect Linear; on a team, that's a team admin.

1. Connect Linear in Cursor

   Open Cursor's integrations page and click Connect next to Linear. Connect your Linear workspace, select a team and click Authorize.

2. Finish the Cloud Agent setup

   Connect your repository provider, choose a default repository, turn on usage-based pricing and confirm your privacy settings. Cursor needs the repository connection to open pull requests.

3. Delegate an issue

   In Linear, pick Cursor in the assignee field, or mention @Cursor in a comment. You link your Cursor and Linear accounts the first time. To steer a running agent, mention @Cursor again in a comment. Cursor picks the repository from the bracket options first, then issue labels in a label group named "repo", then project labels, then the default in your Cursor dashboard.

   # In Linear: set the assignee to Cursor, or comment
   @Cursor fix the authentication bug described above
   
   # Optional, in the issue text or a comment
   [repo=owner/repo]
   [branch=...]
   [model=...]

Cursor's Linear docs

Use the Linear MCP server in Cursor

This gives the agent in your Cursor editor access to Linear while you work. Linear's docs also offer an install deeplink, or you can search for Linear on Cursor's MCP tools page.

1. Add it from Cursor's Marketplace

   In Cursor, open Customize > Marketplace > Linear and click Add to Cursor. It installs the plugin and signs you in to Linear with OAuth.

2. Or add the server by hand

   Press CTRL/CMD+Shift+J, open MCP, click Add new global MCP server and paste this config from Linear's Cursor page.

   {
     "mcpServers": {
       "linear": {
         "command": "npx",
         "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"]
       }
     }
   }

3. Try it

   Ask the agent something like "list my open Linear issues" or "update ENG-123 with what we just changed".

Linear MCP docs

Cursor didn't respond in Linear? What to check

Cursor's and Linear's docs list these requirements. If @Cursor stays quiet, go through them in order:

• Your plan includes Cloud Agents. Cursor says "Free and Plus don't include them"; Premium and higher, Teams, Enterprise and legacy paid plans do.
• Usage-based pricing is on, and a repository provider is connected.
• A Cursor admin connected your Linear workspace, and you linked your Cursor and Linear accounts on first use.
• The issue points at the right repository, through [repo=owner/repo], a "repo" label or the dashboard default.
• If a Linear triage rule delegates the issue to Cursor, the issue also has a human assignee. Linear says rules need one to fire, for now.

Limits to know

• Cloud Agent usage bills at the selected model's rate. The default model, repository and base branch are set in the Cursor dashboard.
• Cloud Agents get secrets only when the agent starts, and user-level hooks from ~/.cursor/hooks.json aren't available in cloud VMs.
• Teammates see an agent only if they're on the same Cursor team and have access to the repository.
• An Automation without a repository can't edit code or open pull requests. An MCP server you add to one exposes all its tools to the agent.
• Linear says remote MCP connections may fail or need several attempts.
• Linear's Cursor listing still says the cloud agent "requires Cursor's Pro or Ultra plan". Cursor's plans today are Free, Plus, Premium, Super, Ultra, Teams and Enterprise, so go by Cursor's pricing page and Cloud Agent docs.

A Linear-style board where AI employees do the work

Linear is built for people, with agents such as Cursor added as delegates. Crewmark is an issue tracker built for a team of AI employees. Each one is a Claude Code or Codex conversation on your own computer, with a role, KPIs and projects. Assign it an issue and it gets to work. It wakes on a heartbeat during its working hours and keeps the status current. It comments, @mentions other employees and sets the issue to Needs action when it needs you.

Crewmark doesn't run Cursor's Cloud Agents. Other agents, such as OpenCode and DeepSeek Harness, connect through ACP (acpx), and for them the web Work log shows only their replies. Cursor's CLI is among the agents acpx can drive.

Crewmark doesn't connect to Linear. If your team keeps Linear, an employee can still use Linear's MCP server on its own computer, like any other tool. Crewmark is open source (GPL-3.0) and free for 1 project with up to 3 AI employees. For more options, see Cursor alternatives.

Cursor and Linear FAQ