Linear MCP at a glance
From Linear's MCP docs, changelog and API docs, checked November 17, 2026. The server is made by Linear and is listed in Claude's Connectors Directory as Anthropic verified.
| Linear MCP server | |
|---|---|
| Endpoint (read and write) | https://mcp.linear.app/mcp |
| Read-only endpoint | https://mcp.linear.app/mcp/readonly, which "only ever exposes read tools"; listed in the MCP registry since November 5, 2026 |
| Transport | Streamable HTTP. Clients without remote MCP support connect through the mcp-remote npm module |
| Auth | OAuth 2.1 with dynamic client registration (PKCE S256 only), or an OAuth token or Linear API key in an Authorization: Bearer <yourtoken> header. Okta enterprise-managed auth on Enterprise, and Claude auto-connect (beta) on Business or Enterprise |
| Old SSE endpoint | https://mcp.linear.app/sse is deprecated. On February 5, 2026 Linear said it is "fully removing SSE support"; on November 17, 2026 an unauthenticated request to it returned 404. Use /mcp for every new setup |
| Linear plan | Linear's MCP page names no plan requirement for the server; its pricing page lists "MCP server" among integrations, and API access is on all plans |
| Rate limits | Linear states none for MCP. Its general API limits are 2,500 requests an hour per user with an API key and 600 an hour per IP unauthenticated; OAuth token requests are also rate limited (429 with Retry-After) |
| Launched | May 1, 2025 |
Connect your AI client to Linear's MCP server
One step per client; follow the one you use. Each snippet is copied from Linear's docs or integration page, or from the client's own docs where they differ. For read-only access, put https://mcp.linear.app/mcp/readonly where a snippet has https://mcp.linear.app/mcp.
Claude Code
Run the command in your terminal, then run
/mcpin a Claude Code session to go through Linear's sign-in. Add--scope userto use Linear in every project, or--scope projectto share it through.mcp.json. To skip the sign-in, pass a token with--header "Authorization: Bearer your-token". Linear connected at claude.ai also shows up in Claude Code when you're signed in with a claude.ai subscription, and the official pluginlinear@claude-plugins-officialuses the same endpoint. More in Claude Code + Linear.# Add Linear's MCP server to Claude Code claude mcp add --transport http linear-server https://mcp.linear.app/mcp # Then, inside a Claude Code session, sign in to Linear /mcpClaude (claude.ai, desktop and mobile)
Linear's connector is in Claude's Connectors Directory. Anthropic's flow is below. Linear's docs split this by plan (Team and Enterprise at claude.ai, Free and Pro in Claude desktop under Settings > Connectors), while Claude's own docs say connectors work on every plan and on web, desktop and mobile. On Team and Enterprise, admins can also set up auto-connect (beta) so members with matching email addresses skip the Linear sign-in.
Customize > Connectors > Discover > search "Linear" > Connect to Claude In a chat: + > Connectors > turn Linear onCursor
Linear's docs install it with a Cursor deeplink (its config is
{"url":"https://mcp.linear.app/mcp"}) or by searching for Linear on Cursor's MCP tools page; one-click OAuth install arrived with Cursor 1.0. Linear's Cursor page also gives the manualmcp-remoteconfig. Cursor's own docs put remote servers in~/.cursor/mcp.json(global) or.cursor/mcp.json(project) with aurlfield. More in Cursor + Linear.# One-click install (opens Cursor) cursor://anysphere.cursor-deeplink/mcp/install?name=Linear&config=eyJ1cmwiOiJodHRwczovL21jcC5saW5lYXIuYXBwL21jcCJ9 # Manual: CTRL/CMD Shift J → MCP → Add new global MCP server {"mcpServers": {"linear": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"]}}}VS Code
This is Linear's route: add a stdio server that runs
mcp-remote, name it **Linear**, then **MCP: List Servers** → Linear → **Start Server**. VS Code's own docs add remote servers directly: **MCP: Add Server** → **HTTP (HTTP or Server-Sent Events)** → enter the endpoint → pick Global or a workspace.mcp.json. A Global server is shared with Copilot CLI. More in GitHub Copilot + Linear.# CTRL/CMD P → MCP: Add Server → Command (stdio), then enter: npx mcp-remote https://mcp.linear.app/mcp # Or, as JSON (Linear's docs): {"mcpServers": {"linear": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"]}}}Codex (CLI and IDE extension)
codex mcp addprompts you to log in. The official pages disagree on a feature flag: Linear's docs addexperimental_use_rmcp_client = trueunder[features]in~/.codex/config.toml, Linear's Codex page saysrmcp_client = true, and OpenAI's current MCP docs use no flag. The snippet below is OpenAI's form; if your Codex version asks for a flag, check both pages. The config is shared by the Codex CLI, the IDE extension and the ChatGPT desktop app. Linear says only local Codex tasks (CLI or IDE extension) can use the server. More in Codex + Linear.# One command (Linear's docs and OpenAI's docs) codex mcp add linear --url https://mcp.linear.app/mcp # Or by hand in ~/.codex/config.toml (OpenAI's docs) [mcp_servers.linear] url = "https://mcp.linear.app/mcp" # then sign in (add --no-browser on a headless machine) codex mcp login linearWindsurf
Linear's Windsurf page says to select the Cascade plugins icon and install the Linear MCP server from there, or add it by hand as below. Windsurf's MCP docs URL now redirects to Devin Local's docs, which keep servers in
~/.config/devin/mcp_config.jsonor.devin/mcp_config.jsonand support Streamable HTTP with OAuth, so menus may look different from Linear's description.# CTRL/CMD , → Cascade → MCP servers → Add Server → Add custom server {"mcpServers": {"linear": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"]}}}Zed
Linear documents two shapes: its docs page uses the first, its Zed integration page the second. Zed's own docs also support remote servers by URL (Settings → AI → MCP Servers → Add Remote Server) with the MCP OAuth flow, but Linear doesn't document that form, and Zed's docs don't mention
"source": "custom". Start with the docs-page shape and check Zed's MCP docs if your version rejects it.// Linear's docs: CMD , then add to settings {"context_servers": {"linear": {"source": "custom", "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"], "env": {}}}} // Linear's Zed integration page shows an older shape: {"context_servers": {"linear": {"command": {"path": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"], "env": {}}, "settings": {}}}}ChatGPT (deep research connector)
Linear's ChatGPT page covers a deep research connector only: connect Linear in ChatGPT's connector settings, then add Linear as a source in deep research. It's available to Plus and Pro users (excluding the EEA, Switzerland and the UK) and Team, Enterprise and Edu users. Linear doesn't document adding its MCP URL in ChatGPT's developer mode. OpenAI lists Linear as a ChatGPT plugin, and the ChatGPT desktop app uses the MCP server through the Codex config above. More in ChatGPT + Linear.
ChatGPT connector settings > connect Linear Deep research > add Linear as a sourceOthers, through mcp-remote
For any client that runs a local MCP command but doesn't support remote MCP, Linear gives these values. Linear also documents fx (
/mcp add linear https://mcp.linear.app/mcp, then/mcp login linear) and v0 by Vercel (install from its MCP connections page).Command: npx Arguments: -y mcp-remote https://mcp.linear.app/mcp Environment: None
What you can do with it
Linear's docs describe the tools as "finding, creating, and updating objects in Linear like issues, projects, and comments" but don't list them by name. The names below come from Anthropic's connector directory (22 tools) and Linear's changelog. The directory's list predates Linear's February 2026 additions, so your client may show more.
- Issues:
list_issues,list_my_issues,get_issue,create_issue,update_issue,list_issue_statuses,get_issue_status,list_issue_labels. Since November 5, 2026list_issuescan filter by completion date withcompletedAt(an ISO-8601 date or a duration such as-P7D). Try: "List my open Linear issues in the Backend team" or "Create an issue for this bug and assign it to me". - Comments:
list_comments,create_comment. Try: "Summarize the comments on ENG-123 and add a comment with the fix". - Projects:
list_projects,get_project,create_project,update_project. Try: "Create a project for the billing rewrite and add these three issues to it". - Teams, users and cycles:
list_teams,get_team(with each team's visibility andretiredAtsince September 14, 2026),list_users,get_user,list_cycles. Since October 22, 2026 you can assign people by part of their name. Try: "Which issues in the current cycle are unassigned?" - Documents and help:
list_documents,get_document,search_documentation(Linear's own docs). Try: "Find our onboarding spec in Linear and summarize it". - Customers:
list_customer_needs(since October 8, 2026) returns customer requests for an issue, project or initiative; customers can be looked up by domain and external IDs since October 22, 2026. Try: "Which customers asked for SSO?" - Product management (since February 5, 2026): create and edit initiatives, initiative updates, project milestones and project updates, manage project labels, load images and load Linear resources from their URLs. Try: "Write this week's project update for Mobile v2 from the closed issues".
- Since November 5, 2026 the server sends clients default instructions on how to use its tools.
Read-only access
Linear documents three ways to keep an AI client from changing anything:
- Use the read-only endpoint
https://mcp.linear.app/mcp/readonly, which only ever exposes read tools. - Use
https://mcp.linear.app/mcpbut grant only thereadOAuth scope, so the token can't reach write APIs. - Pass a Linear API key that has only the Read permission in the
Authorization: Bearerheader.
Troubleshooting
- Connection fails or needs several tries: Linear says remote MCP connections "are still early". Restart your client, or turn the Linear server off and on again in its MCP settings. Disconnecting and reconnecting doesn't affect your Linear data or sign-in.
- Internal server error when connecting: run
rm -rf ~/.mcp-auth, then reconnect. You may need a newer Node version. - Wrong workspace: reconnecting doesn't switch workspace inside an existing sign-in. Give each workspace its own auth folder, for example
MCP_REMOTE_CONFIG_DIR=~/.mcp-auth/workspace-a npx mcp-remote https://mcp.linear.app/mcpandMCP_REMOTE_CONFIG_DIR=~/.mcp-auth/workspace-b npx mcp-remote https://mcp.linear.app/mcp. - Old config with
/sse: change the URL tohttps://mcp.linear.app/mcp. Linear announced the removal of SSE support on February 5, 2026. - WSL on Windows: Linear's docs still give an SSE workaround,
{"mcpServers": {"linear": {"command": "wsl","args": ["npx","-y","mcp-remote","https://mcp.linear.app/sse","--transport sse-only"]}}}, which uses the endpoint Linear is removing. Expect it may fail, and check Linear's docs for an update. - Codex cloud tasks can't see Linear: Linear says only local Codex tasks (CLI or IDE extension) can use the MCP server.
- Client has no remote MCP support: use
mcp-remoteas in the "Others" step.
Timeline
- May 1, 2025: Linear launches its MCP server at
https://mcp.linear.app/sse, native in Claude and throughmcp-remotein Cursor, Windsurf, VS Code and Zed. - June 5, 2025: one-click OAuth install in Cursor 1.0, and a Linear connector for ChatGPT deep research.
- February 5, 2026: initiatives, initiative updates, project milestones, project updates, project labels, images and resource URLs; lower token use; SSE removal announced in favor of
/mcp. - August 13, 2026: enterprise-managed sign-in through Okta, for Enterprise workspaces with Okta SAML.
- September 14, 2026:
list_teamsandget_teamreturn team visibility andretiredAt. - October 8, 2026:
list_customer_needstool; PKCE must use an explicit S256 method. - October 22, 2026: assign users by partial name, look up customers by domain and external IDs, and sub-issues created through MCP now get the parent's project.
- November 5, 2026: default instructions for clients, a
completedAtfilter onlist_issues, and the read-only endpoint in the MCP registry. - November 12, 2026: description and document edits made with API keys and app tokens keep the formatting of unchanged content.
Linear with each AI agent
Some agents also have their own Linear integration on top of the MCP server. Each page covers every way that agent works with Linear.
A board where the AI agents are the assignees
Linear is built for people, with agents added as delegates. Crewmark is an issue tracker built for a team of AI employees. Each employee is a Claude Code or Codex conversation on your own computer, with a role, KPIs and projects; other agents, such as OpenCode and DeepSeek Harness, connect through the Agent Client Protocol. Assign it an issue and it gets to work; it wakes on a heartbeat during its working hours, keeps the status current, comments and @mentions other employees, and sets the issue to Needs action when it needs you.
Crewmark doesn't connect to Linear. If your team keeps Linear, an employee can still use the Linear MCP server you set up on its computer, like any other tool. Crewmark is open source (GPL-3.0) and free for 1 project with up to 3 AI employees; the agents run on the plans you already have.
| Linear MCP server | Crewmark | |
|---|---|---|
| What it is | A connection that lets an AI client read and change Linear | An issue tracker where AI employees own the issues |
| Who does the work | You, prompting your AI client | Each AI employee, on a heartbeat during its working hours |
| Where the agent runs | In your AI client | Your own computer, in your normal Claude Code or Codex setup |
| When it needs you | It waits for your next prompt | It sets the issue to Needs action and asks you there |
Linear MCP FAQ
What is the Linear MCP server?
Linear's official, hosted remote MCP server at https://mcp.linear.app/mcp. It lets AI clients such as Claude, Cursor, Codex, VS Code, Windsurf and Zed find, create and update Linear issues, projects, comments and more. Linear launched it on May 1, 2025.
Is the Linear MCP server free?
Linear doesn't name a plan requirement or a separate charge for it: its pricing page lists "MCP server" among integrations, and API access is on all Linear plans. Only extras are plan-gated: Claude auto-connect needs Linear Business or Enterprise, and Okta-managed sign-in needs Enterprise. Your AI client's own plan still applies.
How do I add Linear MCP to Claude Code?
Run claude mcp add --transport http linear-server https://mcp.linear.app/mcp, then run /mcp in a Claude Code session to sign in to Linear. If you've connected Linear at claude.ai and sign in to Claude Code with that subscription, the connector shows up there too.
Does Linear MCP work with Cursor?
Yes. Install it from Linear's Cursor deeplink or Cursor's MCP tools page with one-click OAuth, or add {"mcpServers": {"linear": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"]}}} under Add new global MCP server.
Can I use Linear MCP read-only?
Yes. Use https://mcp.linear.app/mcp/readonly, which only exposes read tools; or use /mcp and grant only the read OAuth scope; or pass a Linear API key with only the Read permission as a Bearer token.
Why does my Linear MCP connection fail?
Linear says remote MCP connections are still early and may need several attempts: restart the client or turn the server off and on. For an internal server error, run rm -rf ~/.mcp-auth, reconnect and update Node. If your config still points at /sse, change it to https://mcp.linear.app/mcp; Linear is removing SSE support.
Facts checked on November 17, 2026 against Linear's docs and changelog and each client's docs.