Linear Project
NPM · @OPENLY-USEFUL/LINEAR-PROJECT-MCP-SERVER
Scope-gated Linear project administration with optional GitHub and Obsidian evidence adapters
Available components
Last scanned (2 hours ago)
Scores higher than 52% of npm servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 1 of 7 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 73 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1597 tokens (~122/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 −5
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@openly-useful/linear-project-mcp-server@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 7 packages
| Packages resolved | 7 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
github_get_project_evidence Read an Allowlisted GitHub Reference ~62
Read and normalize one allowlisted GitHub repository, commit, pull request, or issue as canonical project evidence. GitHub access is always read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| reference | string | – | – |
| repository | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_bootstrap Bootstrap a Scope-Gated Linear Project ~234
Create or reuse the exact team, project, ACQI-style issue label, and matching project label. Supports an existing team, a dedicated key-bearing team, or a key-bearing subteam. Optionally verifies and links an allowlisted GitHub repository and Obsidian project note, then creates an idempotent first issue with immediate readback.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_writes | boolean | yes | Must be true to acknowledge an external mutation |
| create_obsidian_note | boolean | – | – |
| existing_team_id | string | – | Exact Linear UUID or stable entity ID |
| first_issue | object | – | – |
| github_repository | string | – | – |
| obsidian_note_path | string | – | – |
| parent_team_id | string | – | Exact Linear UUID or stable entity ID |
| project_description | string | – | – |
| project_name | string | yes | – |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| team_key | string | – | Exact allowlisted project scope code, for example ACQI |
| team_mode | string | yes | – |
| team_name | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_capabilities Inspect Linear Project MCP Capabilities ~45
Report configured Linear, GitHub, and Obsidian adapters, exact allowlist coverage, workspace reachability, team-admin support, and whether mutations are enabled. Never writes.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_create_team Create or Resolve a Dedicated Linear Team ~144
Idempotently create a dedicated Linear team whose key exactly equals an allowlisted scope code. Optionally create it as a subteam of an allowlisted parent. Verifies empty issue history on new teams so CODE-1 can be attempted safely.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_workspace_administration | boolean | yes | Must be true to acknowledge an external mutation |
| description | string | – | – |
| key | string | – | Exact allowlisted project scope code, for example ACQI |
| name | string | yes | – |
| parent_team_id | string | – | Exact Linear UUID or stable entity ID |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_find_candidates Find Allowlisted Linear Reconciliation Candidates ~119
Search for potentially related Linear issues, discard results from non-allowlisted teams, and classify whether each candidate is already in the destination project, carries the scope label, or is historical. Never moves or mutates issues.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_project_id | string | yes | Exact Linear UUID or stable entity ID |
| destination_team_id | string | yes | Exact Linear UUID or stable entity ID |
| limit | integer | – | – |
| query | string | yes | – |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_link_evidence Link Verified GitHub or Obsidian Evidence ~190
Verify an allowlisted GitHub reference or allowlisted Obsidian note, confirm the destination issue is inside the exact project and carries the scope label, then add an idempotent evidence link. Does not copy Obsidian note contents into Linear.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_writes | boolean | yes | Must be true to acknowledge an external mutation |
| github_kind | string | – | – |
| github_reference | string | – | – |
| github_repository | string | – | – |
| issue_id | string | yes | Exact Linear UUID or stable entity ID |
| obsidian_note_path | string | – | – |
| project_id | string | yes | Exact Linear UUID or stable entity ID |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| source | string | yes | – |
| team_id | string | yes | Exact Linear UUID or stable entity ID |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_list_scoped_issues List Only Scope-Labeled Project Issues ~105
List issues only when they belong to the exact allowlisted Linear project and carry its exact scope-code issue label. Supports cursor pagination and never writes.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| project_id | string | yes | Exact Linear UUID or stable entity ID |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| team_id | string | yes | Exact Linear UUID or stable entity ID |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_move_candidate Move a Reviewed Issue into the Scoped Project ~205
Move one previously reviewed, allowlisted issue into the exact destination project and apply its scope label. Same-team moves preserve the issue identifier and existing labels. Cross-team moves replace source-team labels and require explicit acknowledgement that the identifier changes. Never changes status or completion.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_team_change | boolean | – | – |
| confirm_identifier_change | boolean | – | – |
| confirm_label_replacement | boolean | – | – |
| confirm_writes | boolean | yes | Must be true to acknowledge an external mutation |
| destination_project_id | string | yes | Exact Linear UUID or stable entity ID |
| destination_team_id | string | yes | Exact Linear UUID or stable entity ID |
| expected_source_project_id | – | yes | – |
| expected_source_team_id | string | yes | Exact Linear UUID or stable entity ID |
| issue_id | string | yes | Exact Linear UUID or stable entity ID |
| reason | string | yes | – |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_resolve_scope Resolve Exact Linear Project Scope ~107
Resolve one allowlisted team, project, issue label, and project label by exact IDs or exact names. Fails on ambiguity and never mutates Linear.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Exact Linear UUID or stable entity ID |
| project_name | string | – | – |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| team_id | string | – | Exact Linear UUID or stable entity ID |
| team_key | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
linear_project_upsert_scoped_issue Upsert an Idempotent Scope-Gated Issue ~180
Create or update exactly one issue inside an allowlisted team and project using a deterministic source marker. Always applies the scope label. Historical records receive the exact [HISTORICAL] title prefix, a HISTORICAL label, and non-actionability metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_writes | boolean | yes | Must be true to acknowledge an external mutation |
| description | string | – | – |
| historical | boolean | – | – |
| project_id | string | yes | Exact Linear UUID or stable entity ID |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| stable_source_marker | string | yes | Deterministic source identity used to make creates idempotent |
| team_id | string | yes | Exact Linear UUID or stable entity ID |
| title | string | yes | – |
| update_existing | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
obsidian_read_project_note Read an Allowlisted Obsidian Project Note ~44
Read one size-limited Markdown note by safe vault-relative path inside the configured Obsidian directory allowlist. Never writes.
| Name | Type | Req | Description |
|---|---|---|---|
| relative_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
obsidian_search_project_notes Search Allowlisted Obsidian Project Notes ~56
Search Markdown notes only inside configured Obsidian directories. Symlinks, traversal, oversized files, and non-Markdown files are excluded. Never writes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
obsidian_upsert_project_note Upsert a Managed Obsidian Project Section ~106
Create or replace only the Openly Useful managed section of an allowlisted Obsidian Markdown note. Preserves all content outside the marker block and requires global writes to be enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_writes | boolean | yes | Must be true to acknowledge an external mutation |
| markdown | string | yes | – |
| relative_path | string | yes | – |
| scope_code | string | yes | Exact allowlisted project scope code, for example ACQI |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | – | – |
| data | – | – | – |
| error | string | – | – |
| ok | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
How do I install the Linear Project MCP server?
Linear Project runs locally as an npm package, launched with npx -y @openly-useful/linear-project-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @openly-useful/linear-project-mcp-server
claude mcp add org-openlyuseful-linear-project -- npx -y @openly-useful/linear-project-mcp-server
What is the Linear Project MCP server?
Linear Project is an MCP server listed in the public MCP registry as org.openlyuseful/linear-project. Scope-gated Linear project administration with optional GitHub and Obsidian evidence adapters. This page covers its npm package (@openly-useful/linear-project-mcp-server).
Is the Linear Project MCP server safe to use?
Linear Project scores 76 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Linear Project MCP server expose?
Linear Project exposes 13 tools: linear_project_capabilities, linear_project_resolve_scope, linear_project_create_team, linear_project_bootstrap, linear_project_list_scoped_issues, and 8 more. Their descriptions and schemas cost roughly 1,597 tokens of context every time the server is loaded.
Is the Linear Project MCP server still maintained?
Linear Project is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Linear Project MCP server under?
Linear Project declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.