Connect Linear to Cursor

Create, update, and search issues across your teams. Add Toolspoke to Cursor once and it can use 11 Linear actions. Your Linear credential stays in Toolspoke, and you choose which actions Cursor may call.

Set it up in Cursor

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Cursor

    ~/.cursor/mcp.json, or .cursor/mcp.json for one project

    { "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }

    Cursor completes the sign-in in a browser tab the first time it connects.

  2. Install Linear and connect it

    Add Linear to a project in your Toolspoke workspace.

    API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Personal API key
    Linear → Settings → Security & access → Personal API keys
  3. Choose what Cursor may do

    All 11 actions start on. Switch off any of the 3 actions that change something in Linear, and Cursor gets a refusal if it tries.

What you can ask Cursor for

A few of the Linear actions that only read, so they are safe to try first.

  • Search issues with any combination of free text, team, assignee, workflow-state type, project, and label
  • List the workspace's teams with their keys and UUIDs
  • List workspace members with their names and email addresses
  • List projects with their state, dates, progress, and lead

What Cursor can do in Linear

8 actions read and 3 write.

Reads

  • Search issues

    Search issues with any combination of free text, team, assignee, workflow-state type, project, and label. Free text matches issue titles and descriptions. Returns compact issue summaries ordered by most recently updated; call get_issue for the full body and comments.

  • Get issue

    Fetch one issue in full: description, current state, assignee, labels, parent and sub-issues, and its most recent comments. Use after search_issues when you need the actual content of an issue.

  • List teams

    List the workspace's teams with their keys and UUIDs. Call this first when you need a team_key for create_issue or search_issues.

  • List workflow states

    List the workflow states (Backlog, Todo, In Progress, Done, …) available on a team, with their category type and UUID. Call this before moving an issue with update_issue so you use a state name the team actually has.

  • List users

    List workspace members with their names and email addresses. Use it to find the assignee_email that create_issue and update_issue expect.

  • List projects

    List projects with their state, dates, progress, and lead. Use it to find the project_id that create_issue and update_issue take.

  • List labels

    List issue labels defined in the workspace or on a specific team, so search_issues can filter by an exact label name.

  • List my issues

    List issues assigned to the owner of the API key, most recently updated first. Completed and cancelled issues are excluded unless include_completed is set. Also returns who the key belongs to.

Writes

  • Create issue

    Create a new issue on a team. Supply team_key (or team_id) plus a title; assignee_email and state_name are resolved for you. Returns the created issue including its identifier and URL.

  • Update issue

    Update an existing issue: retitle it, rewrite the description, move it to another workflow state, reassign it, change priority, or set a due date. Pass at least one field besides id. Does not delete anything.

  • Create comment

    Post a markdown comment on an issue. Use this to report progress or ask a question rather than rewriting the issue description.

Linear in Cursor: questions

Does Cursor see my Linear credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Cursor only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Cursor from changing things in Linear?

Yes. Each of the 11 actions can be switched off for a project. Turn off the 3 that change something and Cursor can only read.

Will 11 actions crowd Cursor's context?

No. Toolspoke shows Cursor five bridge tools, plus a guide where a toolkit has one, and Cursor searches for the Linear action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Should it go in every project or just one?

Either. Put the block in ~/.cursor/mcp.json to have Toolspoke in every project, or in .cursor/mcp.json inside one project to keep it there.

What does it cost?

Tool calls are free on every plan, and a Linear call does not run in a sandbox, so it bills nothing.

Try Linear in Cursor

Free to start, and tool calls cost nothing on any plan.