01 · Records and state owned
Issues, projects, comments and related workspace objects (per MCP docs).
Linear
Linear
Linear runs a centrally hosted first-party MCP server with read-write and read-only endpoints for issues, projects and comments, making it a clean example of scope-separated agent access.
Work & collaborationSystem of recordAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Find and read issues, projects and comments.
03 · Actions and write paths
Create and update issues, projects and comments via the default endpoint.
04 · Authentication and permissions
OAuth 2.1 with dynamic client registration, or bearer token / API key; read-only via /mcp/readonly or read scope.
05 · Monitoring, approval, and recovery
Read-only endpoint and read-scope tokens cannot reach write APIs; Okta enterprise-managed authorization supported.
06 · Limits and caveats
Tool coverage still expanding per Linear.
First-party access
Documented surfaces
Agent access
MCP support
Official MCP serverLinear-hosted remote MCP with read-only endpointCurrent documented service
Support: Official MCP server
Read scope: Issues, projects, comments and related objects.
Write scope: Create and update issues, projects and comments.
Authentication: OAuth 2.1 (DCR), bearer token or API key.
Approval boundary: Writes should require human confirmation in the client.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access3
Identity4
Governance4
Agent access5
UI extensibility3
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Linear ships them.
Single-platform patterns
No specific pattern recorded.
Use in the brief builder →Multi-platform compositions
No specific composition recorded.
Explore composition recipes →Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
2 recorded sources
MCPSource inventory
https://linear.app/docs/mcp ↗First-party Linear MCP server docs.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Oct 31, 2026
Content reopened and reviewed in the 2026-10-31 research refresh.
HomepageSource inventory
https://linear.app/ ↗First-party product homepage.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Oct 31, 2026
Content reopened and reviewed in the 2026-10-31 research refresh.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.