Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldLinear MCPMCP100 SelectedNotion MCPMCP100 Selected
Task fit
Best for
  • Searching and summarizing Linear issues and projects
  • Human-supervised issue, project, and comment updates
  • Read-only planning assistants using Linear's dedicated read-only endpoint
  • Reading and updating explicitly shared Notion pages
  • Markdown-oriented page workflows
  • Teams able to create a dedicated least-privilege integration
Not ideal for
  • Fully autonomous project administration
  • Organizations that cannot authorize third-party MCP clients
  • Workflows requiring Linear capabilities not exposed by the current MCP tools
  • Whole-workspace access without page scoping
  • Stable local-server APIs with no migration monitoring
  • Workflows that only need occasional manual Notion lookup
Avoid when
  • The client cannot securely complete OAuth or protect bearer credentials
  • Issue and roadmap content cannot be shown to the selected AI client or model
  • Write operations cannot be independently reviewed or audited
  • Sensitive workspace content cannot be exposed to the connected model/client
  • You cannot create a dedicated read-only integration or restrict page access
  • You depend on removed pre-2.0 database tool names
Provenance
Provenance details

First-party MCP

Linear · Publisher source ↗

First-party MCP

Notion · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Jul 25, 2026

Package: Jul 25, 2026

Popularity evidence
GitHub starsNot documented

4,594

GitHub stars · checked 2026-08-14T18:46:26.000Z

30-day package downloadsNo reliable download data

624,402

30-day package downloads · checked 2026-07-29T17:30:00.000Z

External adoption evidenceNot documented
  • npm: package downloads: 624,402Exact attributable signal.npm: package downloads · Admission snapshot · checked 2026-07-29T17:30:00.000ZEvidence source ↗
  • github: repository stars: 4,594Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationOAuth 2.1 with dynamic client registration is the primary method. Linear also documents bearer tokens and scoped API keys.The supported hosted service uses OAuth. The documented local server uses NOTION_TOKEN or OPENAPI_MCP_HEADERS; HTTP transport has a separate bearer token and supports carefully configured per-request Notion token passthrough.
CostLinear documents no separate MCP server fee on its setup page. A Linear account is required, and normal plan capabilities, limits, and charges still apply.The local server is MIT licensed. A Notion account and workspace plan are required, and Notion plan/API limits apply; hosted MCP-specific charges were not established in the reviewed materials.
PermissionsThe standard endpoint exposes read and write tools for issues, projects, comments, and related Linear objects under the user's permissions. https://mcp.linear.app/mcp/readonly exposes only read tools, and Linear also documents read-only API keys.Local access is limited by the Notion integration capabilities and pages connected to that integration. Read-only capability is available; write-capable tools can create or update workspace content. Local HTTP transport requires bearer authentication unless an explicitly unsafe flag disables it.
Data handlingAuthorized Linear issue, project, comment, and related workspace data is retrieved by Linear's hosted server and returned to the MCP client. Write calls can change workspace records.Page/database content accessible to the integration can be returned to the MCP client and model. The local server calls Notion APIs; hosted Notion MCP additionally processes requests through Notion's remote service.
Limitations
Tradeoffs
  • Hosted operation removes local server maintenance but places Linear workspace data in the connected AI workflow.
  • The standard endpoint is read-write; the dedicated read-only endpoint materially reduces integrity risk.
  • API keys enable non-interactive use but shift secret storage, scoping, and rotation duties to the operator.
  • Hosted OAuth is actively supported and easier; the local repository warns it may be sunset.
  • Write capability enables useful edits but raises deletion, overwrite, and prompt-injection risk.
  • Version 2 changed database operations to data-source tools, requiring updates to hardcoded prompts.
Risk contextInternal roadmap and issue data can be disclosed, and the default endpoint can modify collaboration records. Prefer the read-only endpoint for research, use least-privilege credentials, and require approval for mutations.Workspace content may be read or modified within the integration's reach. Use a dedicated integration, Read content only where possible, explicitly connect only needed pages, avoid unsafe HTTP auth disabling, and monitor hosted/local migration guidance.
Evidence date
Editorial review2026-07-242026-07-24
Candidate evidence2026-07-29T20:58:26.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →