Skip to main content
Back to the Linear MCP server

MCP Gateway · Cursor

Linear icon

Connect Linear to Cursor

Cursor puts Linear next to the code it describes. Through the Speakeasy MCP Gateway, the Cursor agent can look up the issue behind a branch, plan against the current cycle and keep project docs in step with the work. Hooks let Speakeasy allow or deny each tool call before Cursor runs it.

Category
Project management
Tools
31
Authentication
OAuth
Cursor
Editor and terminal

Behind the MCP Gateway

Run Linear MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Linear call inspected and logged.

Deploy on MCP Gateway

Set up

Add Linear to Cursor in 4 steps

  1. 01

    Add Linear from the catalog

    An admin finds Linear in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Linear uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Linear

    Give teams the mcp:connect scope on the Linear server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Linear to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Linear from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Linear needs its own OAuth grant, so each person connects it once. Until they do, Linear calls fail while the rest of the gateway keeps working.

    From then on, Linear's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Linear

Plan against the current cycle

Ask Cursor what your team has left in the current cycle and which issues block a milestone, so the next task you open in the editor is the one that matters.

list_cycleslist_milestoneslist_issues

Keep the spec next to the code

Open the Linear document for a feature while you implement it, and have Cursor update the document when the design changes during the build.

get_documentupdate_document

Read the screenshots in a bug report

Many bug reports explain the problem with a screenshot. Cursor can fetch the images embedded in an issue or comment and reason about them alongside the code.

get_issueextract_images

Tools

31 tools

Each Linear tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.

get_attachment

Retrieve an attachment's content by ID.

create_attachment

Create a new attachment on a specific Linear issue by uploading base64-encoded content.

delete_attachment

Delete an attachment by ID

list_comments

List comments for a specific Linear issue

save_comment

Create or update a comment on a Linear issue. If id is provided, updates the existing comment; otherwise creates a new one. When creating, issueId and body are required.

delete_comment

Delete a comment from a Linear issue

See all 31 tools

Control

What Speakeasy can see and stop in Cursor

The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.

Tool logs

Gateway

Every Linear call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Linear tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Linear can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

How does a whole engineering team get Linear in Cursor?
A Cursor team admin imports the organization's plugin marketplace and turns on Serve Marketplace From Cursor. Members install the plugin without GitHub access, and the device agent can keep it in place on managed laptops.
What happens if the Speakeasy check fails in Cursor?
Cursor hooks fail closed. If Speakeasy can't allow a prompt or tool call, Cursor doesn't run it.
How do Cursor users get Linear?
An admin adds Linear from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Linear tools their access allows.
Are Linear calls from Cursor logged?
Yes. Linear calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Linear in other clients

AI everywhere.

Control here.