Mcp Linear — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Mcp Linear (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Linear MCP — wraps the Linear GraphQL API (OAuth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
| Tool | Description |
|---|---|
linear_list_issues | Browse issues in your Linear workspace, filtered by TEAM, DATE RANGE, state, priority, assignee, project, cycle, or labels u2014 alone or combined. filter is Linear's own IssueFilter, so anything IssueFilter expresses works here: filter one team ({"team":{"key":{"eq":"ENG"}}}), a date window ({"updatedAt":{"gte":"-P2W"}}), or several DIFFERENT filter sets at once via or. Returns issue ID, title, state, priority, assignee, and URL, newest-updated first. |
linear_get_issue | Get full details of a Linear issue by ID (e.g., "ABC-123"). Returns title, description, state, priority, assignee, labels, comments, and URL. |
linear_create_issue | Create a new issue in Linear with title and optional description. Returns issue ID, key, title, and URL. |
linear_list_teams | List all teams in your Linear workspace. Returns team ID, name, key, and description. |
linear_search | Search Linear issues by keyword or text. Returns matching issues with ID, title, state, priority, and URL. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"linear": {
"url": "https://gateway.pipeworx.io/linear/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/linear/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1865+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.
This pack runs against a connected linear account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect linear, then call POST https://gateway.pipeworx.io/v1/tools/linear_list_issues with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/linear_list_issues. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
@pipeworx/mcp-linear is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/linear/mcp endpoint shown above. It needs network access; there is no offline mode.
{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-linear"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Linear data" })The gateway picks the right tool and fills the arguments automatically.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.