create_issueLABSCO SUMMARY
Issue tracking that keeps up with the conversation.
Because it runs on Linear's official SDK, the parts that usually break in a hand-rolled wrapper — parent/child team inheritance, label sync, cycle filters — come back already correct, so an agent can go from 'what is in this cycle' to a filed subissue in one pass.
What it is
An MCP server built on Linear's official SDK. It talks to Linear with your personal API key and hands back issues with their relationships — parent, children, labels, cycle — already resolved.
What you get
- An issue fetched by ID or key, with its relationships on request
- New issues and subissues, with labels attached and team inherited from the parent
- Existing issues updated across their fields, and assigned to yourself with the keyword
me - Search using Linear's own filters, including by cycle — current, next, previous, or a specific cycle by number or UUID
- Comments added to issues in markdown
- Projects listed, project updates read, and a new project update posted with a health status
Requirements
Bun v1.0.0 or higher, and a Linear account with API access. The personal API key goes in the environment — one variable. Clone and bun run build, then point your client at the built index.js — there is no npx path.
Setup effort
Build from source — git clone https://github.com/cosmix/linear-mcp.git
USE CASES
01
Seeing what is actually in the current cycle
Search with a cycle filter and read the issues that come back with their labels and metadata.
02
Filing the bug while you still remember it
Create the issue with its labels attached, without leaving the thread that found it.
03
Breaking a big ticket into pieces
Read the parent, then create subissues under it — the team is inherited rather than re-picked.
04
Taking something off the unassigned pile
Find the issue, then update it to assign yourself with the keyword me.
05
Closing the loop at the end of the day
Pull the issue by key and update its state and fields in one call.
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. create_issue, update_issue, delete_issue, create_comment and create_project_update change Linear. Cycle filtering is a filter inside search_issues, not a separate tool.
Requires
- Bun v1.0.0 or higher
- 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/cosmix/linear-mcp.git
cd linear-mcp
bun install
bun run buildAdd the mcpServers block to your client config, pointing args at the build/index.js that bun run build just produced
Restart the MCP server (restart Claude Desktop, or restart the server from Cline's MCP settings)
MCP 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>"
}
}
}
}
