Skip to content

Give Cursor access to Linear

You copy ticket details into the editor by hand before every task.

4 stepsModerate
CursorLinearGitHub

How it connects

Your AI reaches your apps through small connectors called MCP servers.
Your AI
Cursor
Connectors
LinearGitHub
Your apps
LinearGitHub

This setup is for developers who plan work in Linear and write code in Cursor. Cursor's agent reads a Linear issue by its ID, plans the change from the description and comments, and opens a GitHub pull request linked back to the issue. You stop copying ticket text into the editor by hand.

Set it up

4 steps. Open one for the details.
  1. 1Add Linear to Cursor

    Open Cursor Settings > MCP (Tools & Integrations in newer versions) and add a new server. Use Linear's remote server URL, https://mcp.linear.app/mcp, in your mcp.json. Save the file and wait for the server to show as connected.

    Tip: Put it in the project's .cursor/mcp.json if only one repo needs Linear, or in your global config for all projects.

  2. 2Authorise your workspace

    When Cursor first calls Linear, a browser window opens for OAuth. Sign in and pick the workspace your team uses, then return to Cursor. Ask the agent to list your assigned issues to confirm it sees the right workspace.

    Tip: If you switch workspaces later, remove and re-add the server to re-authorise.

  3. 3Reference issues in prompts

    In Agent mode, ask Cursor to read an issue by ID, such as ENG-412, and propose a plan before writing code. Check the plan against the issue's acceptance criteria and comments. Then let it make the change in your branch.

    Tip: Ask the agent to post a short progress comment on the Linear issue when it finishes.

  4. 4Open the pull request

    Add GitHub's MCP server with a fine-grained token that can create branches and pull requests in the repository. Ask Cursor to open a PR with the Linear issue ID in the title or branch name. Linear's GitHub integration then links the PR to the issue automatically.

    Tip: Linear's GitHub integration must be enabled in Linear settings for the automatic link.

Then just ask

Things to say once it's connected. Click one to copy it.
Ask Cursor…Cursor

Good to know

What you need, what it won't do, and how to keep it safe.
What you need
  • Cursor with Agent mode
  • A Linear account in the workspace you want to use
  • A GitHub fine-grained token with pull request access
  • Linear's GitHub integration enabled for automatic PR linking
Limits
  • The agent only knows what is in the issue, its comments and your repo; decisions made in meetings stay invisible.
  • OAuth access uses your Linear permissions, so the agent can see every team you can.
  • Long issue threads can take up context space; ask for a summary first on big issues.
Keep it safe
  • Use OAuth rather than a personal API key where possible.
  • Review any issue updates Cursor proposes.
Linear MCP Server (issue-read, issue-write, project-read) GitHub MCP Server (repository-read, issue-write, pull-request-write)

Questions

Straight answers before you start
Which Cursor plan do I need?
MCP servers work in Cursor's Agent mode, which is available on the free and paid plans with different usage limits. Check Cursor's pricing page for current limits.
Can Cursor change Linear issues?
Yes. Linear's MCP server can create and update issues and comments with your account's permissions. Cursor asks before running tool calls unless you enable auto-run.
Does this work in other editors?
Linear's server works with any MCP host, including Claude Code, VS Code and Windsurf. This guide uses Cursor because the steps and settings paths match its interface.
What if the issue description is thin?
The agent plans from what the issue says. Add acceptance criteria and links to designs in Linear first, or give the missing details in your prompt.

Tools in this setup

The products involved