zed-mcp-server-linear

Provides an MCP context server integration for Zed to access Linear (issues, projects, etc.) using either an extension setting (linear_api_key) or the official Linear MCP server endpoint (mcp.linear.app) with a Bearer token header.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ DevTools mcp zed linear context-server agent-panel rust
⚙ Agent Friendliness
52
/ 100
Can an agent use this?
🔒 Security
59
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
55
Error Messages
0
Auth Simplicity
85
Rate Limits
10

🔒 Security

TLS Enforcement
90
Auth Strength
75
Scope Granularity
25
Dep. Hygiene
40
Secret Handling
55

Uses HTTPS MCP endpoint and Authorization: Bearer token for access. The README does not describe scope granularity, secret storage practices, or operational security (e.g., logging/redaction) for the extension; error handling and rate-limit guidance are not documented here.

⚡ Reliability

Uptime/SLA
0
Version Stability
30
Breaking Changes
30
Error Recovery
20
AF Security Reliability

Best When

When you want Linear context inside Zed’s Agent Panel and can safely provide a Linear token for an MCP server.

Avoid When

Avoid if you need strong guarantees about tool error semantics, retries, pagination, or idempotency behavior from the MCP layer, as these details are not provided in the README.

Use Cases

  • Enable Zed Agent Panel to read Linear issues and use them as context for planning/execution
  • Automate issue triage or investigation workflows directly from the Zed agent UI
  • Support agent-assisted project workflows where Linear is the system of record

Not For

  • Workflows requiring offline Linear data or local syncing
  • Teams that cannot obtain/secure a Linear access token
  • Use as a standalone Linear API client outside of Zed/MCP context

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: Bearer token via Authorization header
OAuth: No Scopes: No

README shows two approaches: extension configuration with linear_api_key, and an official MCP server configuration with Authorization: Bearer <token>. Scope granularity and OAuth details are not described.

Pricing

Free tier: No
Requires CC: No

Pricing is not discussed in the provided README content; Linear access/token is implied.

Agent Metadata

Pagination
unknown
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Requires a valid Linear access token; failures will likely occur if token is missing/expired
  • The README does not document MCP tool behaviors (timeouts, retries, rate-limit handling, pagination), so agent robustness may depend on the upstream MCP server implementation
  • Use the official MCP configuration to reduce dependency on the extension; token handling remains your responsibility

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zed-mcp-server-linear.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered