Linear MCP Server – Issues, Projects, and Roadmaps

Linear's official MCP server gives AI agents secure access to supported Linear objects and actions, including issues, projects, comments, initiatives, milestones, updates, and documents. Use it for product planning, engineering coordination, issue management, roadmap maintenance, and status reporting.

#issue-tracking#project-management#roadmaps

Overview

Linear's official MCP server connects compatible AI agents to a user's Linear
workspace through a centrally hosted, authenticated remote service. It gives an
agent structured access to current Linear data and supported actions instead of
limiting the workflow to text copied manually from issues or projects.

What the MCP server enables

Linear documents tools for finding, creating, and updating workspace objects.
Depending on the authenticated user's permissions and the tools exposed by the
server, an AI agent can:

Find, create, and update issues, projects, and comments.
Work with initiatives, project milestones, project updates, and initiative updates.
Manage project labels and retrieve Linear resources through their URLs.
Create and update supported documents associated with Linear work.
Load supported images and attachments for additional issue or project context.
Assist with issue triage, roadmap maintenance, progress reporting, and planning.

When to use it

Use Linear MCP when an agent needs live product-development context or must
perform authorized changes in Linear. Typical workflows include creating issues
from technical findings, updating project status, drafting project or initiative
updates, organizing milestones, summarizing issue activity, maintaining labels,
preparing planning documents, and coordinating work from tools such as coding
assistants or AI chat clients.

Connection and authentication

The supported remote endpoint is https://mcp.linear.app/mcp over Streamable
HTTP. Linear uses OAuth 2.1 with dynamic client registration for the standard
interactive authentication flow.

Linear also supports passing an existing Linear OAuth access token or API key in
the Authorization header as a Bearer token. This can be useful for app users,
restricted read-only access, or integrations that already manage Linear
credentials. Clients that cannot connect to remote MCP servers can use the
documented mcp-remote bridge over stdio.

Key considerations

Access is limited by the authenticated user's workspace permissions and by the
scopes or restrictions of the supplied token. Use the least privilege required,
keep credentials outside source control, and require human confirmation for
write operations. Linear is removing its old SSE endpoint, so new integrations
should use Streamable HTTP. API and MCP usage may also be affected by Linear's
platform rate limits, so avoid unnecessary polling and repeated bulk requests.

Frequently Asked Questions

When should an AI agent use the Linear MCP server?

Use it when a workflow needs live Linear workspace context or authorized changes, such as issue creation, project maintenance, roadmap planning, milestone management, status reporting, comment updates, or document work.

What does the Linear MCP server add to an AI agent's capabilities?

It gives the agent structured access to current Linear data and supported actions, allowing it to find, create, and update workspace objects instead of relying only on static model knowledge or manually pasted context.

What can an AI agent access or manage through Linear MCP?

Depending on permissions and available tools, the agent can work with issues, projects, comments, initiatives, project milestones, project and initiative updates, labels, documents, attachments, and supported resources referenced by Linear URLs.

How is authentication configured for the Linear MCP server?

The standard remote connection uses OAuth 2.1 with dynamic client registration. Linear also supports an existing OAuth access token or API key in the Authorization header as a Bearer token. Credentials should be stored securely and limited to the minimum required scopes or permissions.

Which transport should be used for the Linear MCP server?

Use Streamable HTTP at https://mcp.linear.app/mcp for modern MCP clients. Use the documented mcp-remote stdio bridge only when a client cannot connect directly to a remote MCP endpoint. The deprecated SSE transport is excluded because Linear is removing support for it.