create_issueLABSCO SUMMARY
Issue tracking that keeps up with the conversation.
Cycle filtering is the detail that earns it a place. What is left in this cycle is a question you ask constantly and a query you never want to write by hand.
What it is
A Bun-based MCP server on Linear's official SDK. It creates issues and sub-issues with labels, updates and deletes them with validation, searches using Linear's own filtering, and also reaches projects, project updates and comments.
What you get
- An issue or sub-issue created, with labels and team-inherited parent and child links
- An existing issue updated across its fields, or deleted with validation
- An issue self-assigned using the me keyword
- Issues searched with Linear's filtering, and filtered by cycle — current, next, previous, or one named by number or UUID
- An issue fetched by ID or key, with optional relationships
- Linear projects listed, project updates read, and a project update created with a health status
- Comments added to issues in markdown
- Rate limits handled and errors surfaced rather than swallowed
Requirements
A recent Bun runtime, a Linear account with API access, and that account's API key in the environment. The project is cloned and built locally with bun run build.
Setup effort
Build from source — git clone https://github.com/packetnomad/linear-mcp.git
USE CASES
01
Filing what you just found while debugging
Create the issue with labels and a parent set, without breaking off what you were doing.
02
Seeing what is left in the current cycle
Search filtered to the current cycle rather than reading the board.
03
Updating an issue after the scope changed
Read it with its relationships, then write the new fields back.
04
Picking up the next piece of work
Find an unassigned issue in the cycle and take it with the me keyword.
10 tools
Listed in project docs. Your client may show a different list.
update_issueget_issuesearch_issuesget_teamsdelete_issuecreate_commentget_projectsget_project_updatescreate_project_updateBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
LINEAR_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/packetnomad/linear-mcp.git
cd linear-mcp
bun install
bun run buildMCP Clients
Cline, Claude Desktop
JSON
{
"mcpServers": {
"linear": {
"command": "node",
"args": [
"<YOUR_PATH_TO_LINEAR_MCP>/build/index.js"
],
"env": {
"LINEAR_API_KEY": "<YOUR_LINEAR_API_KEY>"
}
}
}
}
