MCPServerStatus
Home/Directory/app.linear/linear

app.linear/linear

CurrentOFFICIALSource: mcp-registryVerified 8/4/2026

Discovered from Official MCP Registry. Status: active, Version: 1.0.1

MCP server for Linear project management and issue tracking

Company:app.linear
Product:Linear
MCP server for Linear project management and issue tracking
Added:10/11/2026
Last checked:11/11/2026, 5:04:21 PM

Endpoints & Observability

Configured Endpoints

https://mcp.linear.app/sse
sse
Auth: noneMonitoring: DisabledInterval: 5 min
https://mcp.linear.app/mcp
streamable-http
Auth: noneMonitoring: EnabledPrimaryInterval: 60 minLast attempted: 11/11/2026, 5:04:21 PMLast success: 11/11/2026, 5:04:21 PM

Monitoring Status

Online · sign-in required11/11/2026, 5:04:21 PM
Latency14 ms
Protocol VersionN/A
Server NameN/A
Server VersionN/A
ConnectionSuccess
HandshakeFailed
Check Duration14 ms
Server online – this endpoint requires sign-in (auth challenge received)Streamable HTTP error: Error POSTing to endpoint:

Reliability & Incidents

Observed Checks
369
Successful
366
Failed
3
Availability
99.19%
Incidents
1
Downtime
0 min

Latest Incident

Status: RESOLVED10/22/2026, 9:45:43 AM

Endpoint became unhealthy: AUTH_REQUIRED

Resolved at: 10/22/2026, 11:01:20 AM (Duration: min)

Historical Monitoring

Checks Recorded
13
Success
13
Failed
0
Avg Latency
27ms

Status History Timeline

Start of 24hNow

Latency History

Protocol & Compatibility

Protocol

MCP Version
Not observed
Transport
Streamable HTTP
Server Version
Not observed
Last Observed
11/11/2026, 5:04:21 PM

Capabilities

Tools
Not advertised
Resources
Not advertised
Prompts
Not advertised

Compatibility Observations

No historical compatiblity observations found.

Embed badge

MCP server status

Show this server's live status on your site, README or docs.

HTML
Markdown

Security Observations

11/11/2026
Provenance
OFFICIAL via mcp-registry
Endpoint 1
HTTPS
Yes
Transport
sse
Auth Mode
none
Monitoring
Not available
Endpoint 2
HTTPS
Yes
Transport
streamable-http
Auth Mode
none
Monitoring
Available (Monitorable)

About Linear

Linear is a project management and issue tracking tool used by software teams to plan roadmaps, run cycles and track issues, projects and milestones. Linear hosts and manages an official remote MCP server so AI assistants can work with that data directly.

What the Linear MCP server does

The Linear MCP server gives any compatible AI model or agent access to your Linear workspace. Its tools find, create and update Linear objects such as issues, projects and comments, and Linear says more functionality is being added over time. It follows the authenticated remote MCP specification, so nothing runs on your machine.

Linear's own example workflows show the intended use: turning a planning document into a project with issues and milestones, posting standup notes as comments on the matching issues, investigating a reported bug and writing the findings back to the issue, summarizing what a team finished in a cycle, and building a timeline of work around a topic.

Key tools and capabilities

  • Find, create and update issues, projects and comments in your workspace.
  • Read-write access at /mcp by default, or read-only access through /mcp/readonly, which only exposes read tools.
  • Read-only can also be enforced by requesting only the read OAuth scope or by using an API key with only the Read permission.
  • Enterprise-managed authorization through Okta for supported clients such as Claude.
  • A deprecated SSE endpoint at /sse remains as a fallback for clients without streamable HTTP.

Who it's for

  • Engineering teams that want an assistant to file and update issues from planning docs or meeting notes.
  • Engineering managers summarizing completed cycles for status updates.
  • Developers in Cursor, Claude Code, Codex, VS Code, Windsurf or Zed who want issue context while they code.
  • Organizations that need read-only agent access to Linear for reporting.

How to connect

Endpoint
https://mcp.linear.app/mcp
Transport
streamable-http
Auth
OAuth 2.1 or API key

The interactive flow uses OAuth 2.1 with dynamic client registration. You can instead send an OAuth access token or a Linear API key in an Authorization: Bearer header, for example to act as an app user. Each workspace needs its own authentication context. Without credentials the endpoint asks for sign-in, which is what our monitor expects to see.

FAQ

Can I give an AI read-only access to Linear?

Yes. Connect to https://mcp.linear.app/mcp/readonly, request only the read OAuth scope, or use an API key that has only the Read permission.

Why do I get an internal server error when connecting?

Linear suggests clearing saved auth with rm -rf ~/.mcp-auth, retrying, and updating Node if needed.

Can I connect more than one Linear workspace?

Yes, but each workspace needs a separate authentication context, for example a different MCP_REMOTE_CONFIG_DIR per workspace with mcp-remote.

Official links

Based on Linear's official documentation, reviewed 2026-10-26.