streamlinear
A lightweight Linear MCP server for Claude Code that exposes one tool with action dispatch (search, get, update, comment, create, graphql, help) using ~500 tokens instead of the standard MCP's ~17,000.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/prime-radiant-inc/streamlinear with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/prime-radiant-inc/streamlinear'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/prime-radiant-inc--streamlinear)HTML
<a href="/listings/prime-radiant-inc--streamlinear"><img src="/api/listings/prime-radiant-inc--streamlinear/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Single Workspace
Add to your `.mcp.json`:
{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["-y", "@primeradianthq/streamlinear@1.2.1"],
"env": {
"LINEAR_API_TOKEN": "lin_api_xxxxx"
}
}
}
}Multiple Workspaces
To use streamlinear with multiple Linear workspaces, create separate MCP entries and map each secret to `LINEAR_API_TOKEN`:
{
"mcpServers": {
"linear-personal": {
"command": "npx",
"args": ["-y", "@primeradianthq/streamlinear@1.2.1"],
"env": {
"LINEAR_API_TOKEN": "${LINEAR_PERSONAL_TOKEN}"
},
"envFrom": ["LINEAR_PERSONAL_TOKEN"]
},
"linear-work": {
"command": "npx",
"args": ["-y", "@primeradianthq/streamlinear@1.2.1"],
"env": {
"LINEAR_API_TOKEN": "${LINEAR_WORK_TOKEN}"
},
"envFrom": ["LINEAR_WORK_TOKEN"]
}
}
}Installed Package
When installed as a dependency, the package provides two binaries:
npm install @primeradianthq/streamlinear@1.2.1 npx streamlinear-cli help npx streamlinear
The MCP server requires `LINEAR_API_TOKEN` at runtime. Consumers such as Scribble may expose their own operator-facing variable and map it to `LINEAR_API_TOKEN` before starting streamlinear.
Post-Only Mode
Set `STREAMLINEAR_POST_ONLY=1` when confidentiality requires that the agent never read issue content. The server then refuses the read actions (`search`, `get`, and `graphql`) while `create`, `update`, `comment`, and `help` keep working. Internal lookups such as team names and workflow states still happen; they expose workspace metadata, not issue content.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/plugin.json · Manifest · 18 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- {
- "name": "streamlinear",
- "version": "1.2.1",
- "description": "Streamlined Linear integration - one tool, seven actions, zero bloat",
- "author": {
- "name": "Prime Radiant"
- },
- "repository": "https://github.com/prime-radiant-inc/streamlinear",
- "mcpServers": {
- "linear": {
- "command": "node",
- "args": ["${CLAUDE_PLUGIN_ROOT}/mcp/dist/index.js"],
- "env": {
- "LINEAR_API_TOKEN": "${LINEAR_API_TOKEN}"
- }
- }
- }
- }
README.md · README · 125 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # streamlinear
- A lightweight Linear MCP for Claude Code. One tool, seven actions.
- ## Why?
- The standard Linear MCP uses ~17,000 tokens for tool definitions.
- streamlinear uses ~500 tokens.
- ## Design Philosophy
- Instead of 23 separate tools, streamlinear has **one tool with action dispatch**:
- ```json
- {"action": "search"}
- {"action": "get", "id": "ABC-123"}
- {"action": "update", "id": "ABC-123", "state": "Done"}
- {"action": "comment", "id": "ABC-123", "body": "Fixed!"}
- {"action": "create", "title": "New bug", "team": "ENG"}
- {"action": "graphql", "graphql": "query { viewer { name } }"}
- {"action": "help"}
- ```
- ## Actions
- | Action | Purpose |
- |--------|---------|
- | `search` | Find issues (smart defaults: your active issues) |
- | `get` | Issue details by ABC-123, URL, or UUID |
- | `update` | Change state, priority, assignee |
- | `comment` | Add comment to issue |
- | `create` | Create new issue |
- | `graphql` | Raw GraphQL for anything else |
- | `help` | Full documentation |
- ## Installation
- ### Single Workspace
- Add to your `.mcp.json`:
- ```json
- {
- "mcpServers": {
- "linear": {
- "command": "npx",
- "args": ["-y", "@primeradianthq/streamlinear@1.2.1"],
- "env": {
- "LINEAR_API_TOKEN": "lin_api_xxxxx"
- }
- }
- }
- }
- ```
- ### Multiple Workspaces
- To use streamlinear with multiple Linear workspaces, create separate MCP entries and map each secret to `LINEAR_API_TOKEN`:
- ```json
- {
- "mcpServers": {
- "linear-personal": {
- "command": "npx",
- "args": ["-y", "@primeradianthq/streamlinear@1.2.1"],
- "env": {
- "LINEAR_API_TOKEN": "${LINEAR_PERSONAL_TOKEN}"
- },
- "envFrom": ["LINEAR_PERSONAL_TOKEN"]
- },
- "linear-work": {
- "command": "npx",
- "args": ["-y", "@primeradianthq/streamlinear@1.2.1"],
- "env": {
- "LINEAR_API_TOKEN": "${LINEAR_WORK_TOKEN}"
- },
- "envFrom": ["LINEAR_WORK_TOKEN"]
- }
- }
- }
- ```
- ### Installed Package
- When installed as a dependency, the package provides two binaries:
- ```bash
- npm install @primeradianthq/streamlinear@1.2.1
- npx streamlinear-cli help
- npx streamlinear
- ```
- The MCP server requires `LINEAR_API_TOKEN` at runtime. Consumers such as Scribble may expose their own operator-facing variable and map it to `LINEAR_API_TOKEN` before starting streamlinear.
- ### Post-Only Mode
- Set `STREAMLINEAR_POST_ONLY=1` when confidentiality requires that the agent never read issue content. The server then refuses the read actions (`search`, `get`, and `graphql`) while `create`, `update`, `comment`, and `help` keep working. Internal lookups such as team names and workflow states still happen; they expose workspace metadata, not issue content.
- ## Smart Defaults
- - Teams and workflow states shown in tool description (fetched at startup)
- - `search` with no params → your assigned issues, not completed/canceled
- - IDs accept ABC-123, Linear URLs, or UUIDs
- - State names are fuzzy matched ("done" → "Done", "in prog" → "In Progress")
- - `assignee: "me"` uses the authenticated user
- - `@name` in create descriptions and comment bodies becomes a Linear profile link when it matches exactly one workspace user
- - Error messages show valid options when things fail
- ## The GraphQL Escape Valve
- For anything not covered by the main actions, use raw GraphQL:
- ```json
- {
- "action": "graphql",
- "graphql": "query { projects { nodes { id name } } }"
- }
- ```
- Use `{"action": "help"}` for common GraphQL patterns.
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.