ISSUE TRACKING / Linear
Linear MCP
Finds and updates Linear issues, projects and comments, with a dedicated endpoint for read-only tools.
“Linear’s MCP server follows the authenticated remote MCP spec, so the server is centrally hosted and managed.”
01 / THE REASONING
Why this made the selection.
- A separate read-only endpoint gives an inspection workflow a concrete configuration choice.
- The documented permissions distinguish tool availability from the OAuth/API-token rights behind it.
- Linear’s page describes a remote Streamable HTTP server that authenticates each session with OAuth, with bearer-token or API-key authentication also documented.
- The same page offers a readonly endpoint that only exposes read tools, and says a read-scoped token cannot reach write APIs.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- https://linear.app/docs/mcp (setup, access and capability sections)
- https://linear.app/docs/mcp
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- https://mcp.linear.app/mcp/readonly exposes only read tools; a read-only OAuth scope or limited API key is another documented route.
- The /sse endpoint is a deprecated fallback, so new setups should use Streamable HTTP.
- The page says the Linear MCP server authenticates each session via OAuth and uses Streamable HTTP, and that a bearer token or Linear API key is an alternative.
- Because reconnecting does not switch workspaces inside one auth session, each workspace needs its own authentication context.
- Read-only access is a separate endpoint that only exposes read tools, or a read OAuth scope whose token cannot reach write APIs. Clients that do not support remote MCP are not served by the remote endpoint alone.
- The guide documents enterprise-managed MCP authorization through an Okta identity-provider setting and issuer URI.
Not established by this review
- Authentication, service availability and tool execution were not tested.
- The hosted implementation source and licence were not established.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- For inspection, add https://mcp.linear.app/mcp/readonly; use https://mcp.linear.app/mcp only when writes are intended.
- Complete OAuth or configure a limited API key through the client’s credential mechanism.
Before you start
- A Linear account with the intended workspace access.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"linear": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.linear.app/mcp"
]
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://linear.app/docs/mcp
Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample