# @mrfentmen/linear-mcp

Query the Linear GraphQL API (key; set LINEAR_API_KEY, raw Authorization): viewer, teams, issue search.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.2
- **Author:** Unknown
- **License:** MIT
- **npm:** @mrfentmen/linear-mcp
- **Source:** https://github.com/mrfentmen/premium-mcps
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 2 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-03T06:28:11.468Z
- **Version scanned:** 1.1.2
- **CVEs:** none found by OSV at scan time

## Tools

12 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `me` — The Linear user the API key belongs to.
- `list_teams` — Teams in the workspace, with key and id.
- `search_issues` — Search issues by text, e.g. login bug.
- `get_issue` — Issue details.
- `team_issues` — Issues in a team.
- `list_projects` — Linear projects.
- `my_issues` — Assigned to me.
- `list_labels` — Team labels.
- `create_issue` — Create a REAL issue.
- `update_issue_title` — Rename a REAL issue.
- `package_adoption` — How much an npm package is actually used and how recently it shipped: monthly download count, dist-tags, release cadence, deprecation count and maintainers. No 
- `project_scorecard` — The OpenSSF scorecard for a repository: the aggregate supply-chain score and the individual checks behind it, worst first, with the reason each one gives.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"linear\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@mrfentmen/linear-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40mrfentmen%2Flinear-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40mrfentmen%2Flinear-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mrfentmen%2Flinear-mcp
- HTML page: https://forgeregistry.com/registry/%40mrfentmen%2Flinear-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.