
A streamable HTTP gateway that wraps Linear's GraphQL API with OAuth authentication, letting Claude interact with your Linear workspace through Pipeworx's infrastructure. The server is part of a larger gateway offering 673+ data sources, so you can either use it standalone or tap into the full Pipeworx suite. Instead of calling specific tools, you can use ask_pipeworx to query Linear data in plain English and let the gateway handle tool selection and argument mapping. Useful if you want Claude to read issues, update tasks, or pull project data without managing OAuth flows yourself. The exact tool list isn't documented in the repo, but it's a GraphQL wrapper so expect standard Linear operations like querying issues, teams, and projects.
Public tool metadata for what this MCP can expose to an agent.
list_commentsList comments for a specific Linear issue1 paramsList comments for a specific Linear issue
issueIdstringcreate_commentCreate a comment on a specific Linear issue3 paramsCreate a comment on a specific Linear issue
bodystringissueIdstringparentIdstringlist_cyclesRetrieve cycles for a specific Linear team2 paramsRetrieve cycles for a specific Linear team
teamIdstringtypestringcurrent · previous · nextget_documentRetrieve a Linear document by ID or slug1 paramsRetrieve a Linear document by ID or slug
idstringlist_documentsList documents in the user's Linear workspace11 paramsList documents in the user's Linear workspace
afterstringbeforestringcreatedAtstringcreatorIdstringincludeArchivedbooleaninitiativeIdstringlimitnumberorderBystringcreatedAt · updatedAtdefault: updatedAtprojectIdstringquerystringupdatedAtstringcreate_documentCreate a new document in Linear5 paramsCreate a new document in Linear
colorstringcontentstringiconstringprojectstringtitlestringupdate_documentUpdate an existing Linear document6 paramsUpdate an existing Linear document
colorstringcontentstringiconstringidstringprojectstringtitlestringget_issueRetrieve detailed information about an issue by ID, including attachments and git branch name2 paramsRetrieve detailed information about an issue by ID, including attachments and git branch name
idstringincludeRelationsbooleanlist_issuesList issues in the user's Linear workspace. For my issues, use "me" as the assignee.16 paramsList issues in the user's Linear workspace. For my issues, use "me" as the assignee.
afterstringassigneestringbeforestringcreatedAtstringcyclestringdelegatestringincludeArchivedbooleanlabelstringlimitnumberorderBystringcreatedAt · updatedAtdefault: updatedAtparentIdstringprojectstringquerystringstatestringteamstringupdatedAtstringcreate_issueCreate a new Linear issue18 paramsCreate a new Linear issue
assigneestringblockedByarrayblocksarraycyclestringdelegatestringdescriptionstringdueDatestringduplicateOfstringlabelsarraylinksarraymilestonestringparentIdstringprioritynumberprojectstringrelatedToarraystatestringteamstringtitlestringupdate_issueUpdate an existing Linear issue19 paramsUpdate an existing Linear issue
assigneestringblockedByarrayblocksarraycyclestringdelegatestringdescriptionstringdueDatestringduplicateOfstringestimatenumberidstringlabelsarraylinksarraymilestonestringparentIdstringprioritynumberprojectstringrelatedToarraystatestringtitlestringlist_issue_statusesList available issue statuses in a Linear team1 paramsList available issue statuses in a Linear team
teamstringget_issue_statusRetrieve detailed information about an issue status in Linear by name or ID3 paramsRetrieve detailed information about an issue status in Linear by name or ID
idstringnamestringteamstringlist_issue_labelsList available issue labels in a Linear workspace or team6 paramsList available issue labels in a Linear workspace or team
afterstringbeforestringlimitnumbernamestringorderBystringcreatedAt · updatedAtdefault: updatedAtteamstringcreate_issue_labelCreate a new Linear issue label6 paramsCreate a new Linear issue label
colorstringdescriptionstringisGroupbooleannamestringparentIdstringteamIdstringlist_projectsList projects in the user's Linear workspace12 paramsList projects in the user's Linear workspace
afterstringbeforestringcreatedAtstringincludeArchivedbooleaninitiativestringlimitnumbermemberstringorderBystringcreatedAt · updatedAtdefault: updatedAtquerystringstatestringteamstringupdatedAtstringget_projectRetrieve details of a specific project in Linear1 paramsRetrieve details of a specific project in Linear
querystringcreate_projectCreate a new project in Linear13 paramsCreate a new project in Linear
colorstringdescriptionstringiconstringinitiativestringlabelsarrayleadstringnamestringpriorityintegerstartDatestringstatestringsummarystringtargetDatestringteamstringupdate_projectUpdate an existing Linear project13 paramsUpdate an existing Linear project
colorstringdescriptionstringiconstringidstringinitiativesarraylabelsarrayleadstringnamestringpriorityintegerstartDatestringstatestringsummarystringtargetDatestringlist_project_labelsList available project labels in the Linear workspace5 paramsList available project labels in the Linear workspace
afterstringbeforestringlimitnumbernamestringorderBystringcreatedAt · updatedAtdefault: updatedAtlist_teamsList teams in the user's Linear workspace8 paramsList teams in the user's Linear workspace
afterstringbeforestringcreatedAtstringincludeArchivedbooleanlimitnumberorderBystringcreatedAt · updatedAtdefault: updatedAtquerystringupdatedAtstringget_teamRetrieve details of a specific Linear team1 paramsRetrieve details of a specific Linear team
querystringlist_usersRetrieve users in the Linear workspace2 paramsRetrieve users in the Linear workspace
querystringteamstringget_userRetrieve details of a specific Linear user1 paramsRetrieve details of a specific Linear user
querystringsearch_documentationSearch Linear's documentation to learn about features and usage2 paramsSearch Linear's documentation to learn about features and usage
pagenumberquerystringLinear MCP — wraps the Linear GraphQL API (OAuth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
linear_list_issues | Browse issues in your Linear workspace with optional filters by state, priority, or assignee. Returns issue ID, title, state, priority, assignee, and URL. |
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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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