CookiesForAI

Linear MCP server

The Linear MCP server gives AI agents access to your Linear workspace through Linear's hosted endpoint: find, create and update issues, projects and comments, with a read-only URL when you only need lookups.

By Linear Official · Updated

Connect Linear

Claude Code

Terminal
claude mcp add --transport http linear-server https://mcp.linear.app/mcp

Codex (then run: codex mcp login linear)

Terminal
codex mcp add linear --url https://mcp.linear.app/mcp

VS Code or Windsurf, through mcp-remote

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

Read-only server URL

Terminal
https://mcp.linear.app/mcp/readonly

Cursor installs Linear from its MCP tools directory, and Claude Desktop and Claude.ai add it as a connector in Settings. Jules uses a Linear API key pasted into its MCP settings.

What the Linear MCP server does

The Linear MCP server is Linear's own hosted server for connecting AI agents to a Linear workspace. Once signed in, an agent can look up issues, projects and comments, create new issues, change status, assignee or labels, and post comments, all with the permissions of the account that authorized it. Linear publishes no source code for it: it is a remote service only.

Linear serves the MCP server at two URLs. The default one at mcp.linear.app/mcp can read and write; the one ending in /mcp/readonly allows lookups only, which suits agents that should report on work but never change it. Sign-in is OAuth 2.1 in an interactive flow, and Linear also accepts a Linear API key or bearer token in the Authorization header for clients and automations that cannot open a browser.

Linear documents setup for Claude Code, Codex, Cursor, Claude Desktop and Claude.ai connectors, VS Code, Windsurf, Zed, Jules and v0, and gives the mcp-remote proxy command for any other client that only runs local servers. The deprecated SSE endpoint at /sse still exists as a fallback. The server is listed in the official MCP Registry as app.linear/linear.

When to use Linear

  • You want the coding agent to read the Linear issue it is fixing and move it to Done.
  • You want to file a bug report from an error the agent just found.
  • You need a summary of a project's open issues or a cycle's progress.
  • You want a read-only reporting agent that can never edit issues.

When to pick something else

  • Agents you do not watch on the default URL: it can create and edit issues as you, so use the /mcp/readonly URL when lookups are enough.
  • Self-hosting or auditing the code: Linear publishes no source, so you cannot run or inspect the server yourself.

What Linear needs

  • A Linear account in the workspace you want to connect
  • Node.js only for clients that connect through the mcp-remote proxy

What the Linear MCP server costs

Linear's docs list no separate charge or plan restriction for the server; Linear has a Free plan and paid per-user plans.

Current prices: linear.app . We do not list prices: vendors change them often, so check the publisher's own page.

  • Atlassian: The Atlassian MCP server gives AI agents access to Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom on Atlassian Cloud: search, summarize, and create or update issues and pages.
  • Notion: The Notion MCP server gives AI agents access to your Notion workspace through Notion's hosted server: search pages and databases, read them as Markdown, and create or update pages, databases and views.
  • Obsidian: The Obsidian MCP server gives AI agents access to your Obsidian vault through the Local REST API plugin: list and read notes, search across files, append or patch content and delete files.
  • Slack: The Slack MCP server gives AI agents access to a Slack workspace through Slack's hosted endpoint: search messages and files, read channels and threads, send messages, and edit canvases and lists.