Overview
What Linear MCP Server does
Linear's official remote MCP server lets agents work with planning and issue-tracking context while honoring the signed-in user's workspace access. Beyond issues, projects, and comments, the current service supports initiatives, milestones, project and initiative updates, labels, documents, images, and URL-addressable Linear resources. The modern endpoint uses Streamable HTTP with OAuth 2.1 dynamic client registration. API keys and existing OAuth access tokens can also be supplied as Bearer tokens for automation or constrained read-only access.
Best for
- Turning engineering or product conversations into tracked Linear work
- Reading project context and preparing progress updates from an AI client
- Automations that need a centrally hosted, first-party Linear integration
Not ideal for
- Offline use or self-hosting inside a private network
- Broad autonomous edits without workspace permissions and agent confirmation policies
Capabilities
What an agent can do
- 01
Find, create, and update issues, projects, comments, and related workspace objects
- 02
Manage initiatives, milestones, project updates, initiative updates, and labels
- 03
List and create documents under supported Linear entities
- 04
Load images and resolve Linear resource URLs into agent context
- 05
Authenticate interactive users or automation identities through the hosted endpoint
Representative tools and operations
save_issuelist_commentssave_projectsave_documentlist_userslist_issue_labels
Installation
Connect Linear MCP Server
Use the publisher’s current instructions as the source of truth. The examples below were checked on .
Claude CodeAdd Linear's hosted endpoint
claude mcp add --transport http linear-server https://mcp.linear.app/mcpRun /mcp after opening a Claude Code session and complete the Linear authorization flow.CodexRegister and authorize Linear
codex mcp add linear --url https://mcp.linear.app/mcpAfter adding the server, run `codex mcp login linear` if the client does not open authorization automatically.Legacy stdio-only clientsBridge the Streamable HTTP endpoint
npx -y mcp-remote https://mcp.linear.app/mcp{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"]
}
}
}Trust and access
Authentication and security notes
Authentication: OAuth 2.1 with dynamic client registration is the default. Linear also accepts a personal API key or OAuth access token in the Authorization Bearer header.
Review before connecting
- OAuth inherits the user's workspace permissions; use a restricted API key or app identity when automation needs narrower access.
- Issue, project, document, and update tools can create visible team activity, so require confirmation for high-impact changes.
- Do not paste personal API keys into committed configuration; send them through a protected Bearer header or client secret facility.
Known limitations
- The service is hosted by Linear and cannot be self-hosted.
- Tool results and mutations are limited by the authenticated identity's workspace and object permissions.
- The older SSE endpoint is being removed; new configurations should use /mcp.
- Available objects and tool parameters evolve with Linear's hosted release rather than a pinned local server version.
Evidence
Sources used for this guide
Facts were checked against primary publisher material. Descriptions and guidance are original Graphify summaries.
FAQ
Questions about Linear MCP Server
Can Linear MCP use an API key instead of interactive OAuth?
Yes. The endpoint accepts Linear API keys and OAuth access tokens as Bearer credentials, which is useful for app users and constrained automation.
Should new clients use Linear's /sse endpoint?
No. Linear is retiring SSE. New and updated configurations should use https://mcp.linear.app/mcp with Streamable HTTP.
