# Linear Project (npm · @openly-useful/linear-project-mcp-server)

Scope-gated Linear project administration with optional GitHub and Obsidian evidence adapters

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@openly-useful/linear-project-mcp-server`: 80/100 (this document), [markdown](https://verifymcp.io/servers/org-openlyuseful-linear-project/openly-useful-linear-project-mcp-server.md), [page](https://verifymcp.io/servers/org-openlyuseful-linear-project/openly-useful-linear-project-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@openly-useful/linear-project-mcp-server`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 1 of 6 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 47% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add org-openlyuseful-linear-project -- npx -y @openly-useful/linear-project-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "org-openlyuseful-linear-project": {
      "command": "npx",
      "args": [
        "-y",
        "@openly-useful/linear-project-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-openlyuseful-linear-project": {
      "command": "npx",
      "args": [
        "-y",
        "@openly-useful/linear-project-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add org-openlyuseful-linear-project -- npx -y @openly-useful/linear-project-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-openlyuseful-linear-project": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@openly-useful/linear-project-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-openlyuseful-linear-project --command npx --arg -y --arg @openly-useful/linear-project-mcp-server
```

### Hermes

```yaml
mcp_servers:
  org-openlyuseful-linear-project:
    command: "npx"
    args: ["-y", "@openly-useful/linear-project-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "org-openlyuseful-linear-project": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@openly-useful/linear-project-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-openlyuseful-linear-project -t stdio -c npx -a -y @openly-useful/linear-project-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "org-openlyuseful-linear-project": {
      "command": "npx",
      "args": [
        "-y",
        "@openly-useful/linear-project-mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `linear_project_capabilities` (~45 tokens)

Inspect Linear Project MCP Capabilities

Report configured Linear, GitHub, and Obsidian adapters, exact allowlist coverage, workspace reachability, team-admin support, and whether mutations are enabled. Never writes.

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `linear_project_resolve_scope` (~107 tokens)

Resolve Exact Linear Project Scope

Resolve one allowlisted team, project, issue label, and project label by exact IDs or exact names. Fails on ambiguity and never mutates Linear.

Input parameters:

- `project_id` (string): Exact Linear UUID or stable entity ID
- `project_name` (string)
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI
- `team_id` (string): Exact Linear UUID or stable entity ID
- `team_key` (string)

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `linear_project_create_team` (~144 tokens)

Create or Resolve a Dedicated Linear Team

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.

Input parameters:

- `confirm_workspace_administration` (boolean, required): Must be true to acknowledge an external mutation
- `description` (string)
- `key` (string): Exact allowlisted project scope code, for example ACQI
- `name` (string, required)
- `parent_team_id` (string): Exact Linear UUID or stable entity ID
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `linear_project_bootstrap` (~234 tokens)

Bootstrap a Scope-Gated Linear Project

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.

Input parameters:

- `confirm_writes` (boolean, required): 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, required)
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI
- `team_key` (string): Exact allowlisted project scope code, for example ACQI
- `team_mode` (string, required)
- `team_name` (string)

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `linear_project_list_scoped_issues` (~105 tokens)

List Only Scope-Labeled Project Issues

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.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `project_id` (string, required): Exact Linear UUID or stable entity ID
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI
- `team_id` (string, required): Exact Linear UUID or stable entity ID

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `linear_project_upsert_scoped_issue` (~180 tokens)

Upsert an Idempotent Scope-Gated Issue

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.

Input parameters:

- `confirm_writes` (boolean, required): Must be true to acknowledge an external mutation
- `description` (string)
- `historical` (boolean)
- `project_id` (string, required): Exact Linear UUID or stable entity ID
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI
- `stable_source_marker` (string, required): Deterministic source identity used to make creates idempotent
- `team_id` (string, required): Exact Linear UUID or stable entity ID
- `title` (string, required)
- `update_existing` (boolean)

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `linear_project_find_candidates` (~119 tokens)

Find Allowlisted Linear Reconciliation Candidates

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.

Input parameters:

- `destination_project_id` (string, required): Exact Linear UUID or stable entity ID
- `destination_team_id` (string, required): Exact Linear UUID or stable entity ID
- `limit` (integer)
- `query` (string, required)
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `linear_project_move_candidate` (~205 tokens)

Move a Reviewed Issue into the Scoped Project

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.

Input parameters:

- `allow_team_change` (boolean)
- `confirm_identifier_change` (boolean)
- `confirm_label_replacement` (boolean)
- `confirm_writes` (boolean, required): Must be true to acknowledge an external mutation
- `destination_project_id` (string, required): Exact Linear UUID or stable entity ID
- `destination_team_id` (string, required): Exact Linear UUID or stable entity ID
- `expected_source_project_id` (required)
- `expected_source_team_id` (string, required): Exact Linear UUID or stable entity ID
- `issue_id` (string, required): Exact Linear UUID or stable entity ID
- `reason` (string, required)
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `linear_project_link_evidence` (~190 tokens)

Link Verified GitHub or Obsidian Evidence

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.

Input parameters:

- `confirm_writes` (boolean, required): Must be true to acknowledge an external mutation
- `github_kind` (string)
- `github_reference` (string)
- `github_repository` (string)
- `issue_id` (string, required): Exact Linear UUID or stable entity ID
- `obsidian_note_path` (string)
- `project_id` (string, required): Exact Linear UUID or stable entity ID
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI
- `source` (string, required)
- `team_id` (string, required): Exact Linear UUID or stable entity ID
- `title` (string, required)

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `github_get_project_evidence` (~62 tokens)

Read an Allowlisted GitHub Reference

Read and normalize one allowlisted GitHub repository, commit, pull request, or issue as canonical project evidence. GitHub access is always read-only.

Input parameters:

- `kind` (string, required)
- `reference` (string)
- `repository` (string, required)

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `obsidian_search_project_notes` (~56 tokens)

Search Allowlisted Obsidian Project Notes

Search Markdown notes only inside configured Obsidian directories. Symlinks, traversal, oversized files, and non-Markdown files are excluded. Never writes.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `obsidian_read_project_note` (~44 tokens)

Read an Allowlisted Obsidian Project Note

Read one size-limited Markdown note by safe vault-relative path inside the configured Obsidian directory allowlist. Never writes.

Input parameters:

- `relative_path` (string, required)

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

### `obsidian_upsert_project_note` (~106 tokens)

Upsert a Managed Obsidian Project Section

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.

Input parameters:

- `confirm_writes` (boolean, required): Must be true to acknowledge an external mutation
- `markdown` (string, required)
- `relative_path` (string, required)
- `scope_code` (string, required): Exact allowlisted project scope code, for example ACQI
- `title` (string, required)

Output parameters:

- `audit` (object)
- `data`
- `error` (string)
- `ok` (boolean)
- `summary` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/org-openlyuseful-linear-project/openly-useful-linear-project-mcp-server#diagnostics

## Score history

- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 75
- 2026-09-08: 75
- 2026-09-07: 74
- 2026-09-06: 74
- 2026-09-05: 73
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 67
- 2026-08-29: 67
- 2026-08-28: 67
- 2026-08-27: 67
- 2026-08-26: 67
- 2026-08-25: 65
- 2026-08-24: 65
- 2026-08-23: 65

## Common questions

### 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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.

## Links

- npm package: https://www.npmjs.com/package/@openly-useful/linear-project-mcp-server
- Socket report: https://socket.dev/npm/package/@openly-useful/linear-project-mcp-server
- Repository: https://github.com/Openly-Useful/linear-project-skills
- Website: https://github.com/Openly-Useful/linear-project-skills/tree/main/mcp/linear-project-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/org-openlyuseful-linear-project/openly-useful-linear-project-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-openlyuseful-linear-project/openly-useful-linear-project-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/org-openlyuseful-linear-project/openly-useful-linear-project-mcp-server