线性 MCP 服务器
线性 API的模型上下文协议服务器。
旨在比现有的 Linear MCP 服务器功能更丰富，并旨在通过 Claude 进行整体项目管理。
这是基于https://github.com/jerhadf/linear-mcp-server的，具有更多功能。
特征：
安装
将服务器配置添加到 Claude Desktop。
注意：Claude 与 nvm 环境兼容。请确保使用 Node 的绝对路径来引用其版本。
{
"mcpServers": {
"linear": {
"command": "/Users/USERNAME/.nvm/versions/node/v22.13.0/bin/node",
"args": [
"--experimental-strip-types",
"/absolute/path/to/repo/index.ts"
],
"env": {
"LINEAR_API_KEY": "your_linear_api_key_here"
}
}
}
}
可用工具
项目管理
create-project - 创建一个新的 Linear 项目view-project - 通过 ID 查看线性项目update-project - 更新线性项目
主动管理
create-initiative - 创建一个新的线性计划view-initiative - 按 ID 查看线性倡议update-initiative - 更新线性倡议
问题管理
create-issue - 创建一个新的线性问题view-issue - 通过 ID 查看线性问题update-issue - 更新线性问题search-issues - 搜索线性问题
问题关系
create-issue-relation - 在两个问题（阻止、重复等）之间创建关系view-issue-relations - 查看给定问题的所有关系delete-issue-relation - 删除两个问题之间的关系
例子
User:
Break the Implement Contact API Endpoints issue into multiple issues, one for each endpoint
Claude:
I'll break down the API endpoints issue into separate issues for each endpoint and create the appropriate relationships.
View result from create-issue from linear (local)
View result from create-issue from linear (local)
View result from create-issue from linear (local)
View result from create-issue from linear (local)
View result from create-issue from linear (local)
Now let's create the relationships between these new issues and the existing ones. First, they all depend on the TypeScript Models issue:
View result from create-issue-relation from linear (local)
View result from create-issue-relation from linear (local)
View result from create-issue-relation from linear (local)
View result from create-issue-relation from linear (local)
View result from create-issue-relation from linear (local)
I've created five separate issues for each endpoint and set up their relationships:
GET /contacts (List) - d1aae514
GET /contacts/:id (Single) - 01850d5d
POST /contacts (Create) - 2e0f2b75
PUT /contacts/:id (Update) - d22b143d
DELETE /contacts/:id (Delete) - dde30779
All of these endpoints depend on the TypeScript Models issue (2c38c6ee) being completed first.
The UI Components issue (dd214884) and Search/Filter issue (81a33a29) now should depend on the completion of these endpoint issues, particularly the GET endpoints.
Would you like me to:
Create those additional relationships with the UI Components?
Add any specific cross-dependencies between the endpoints themselves?
Break down any of these endpoint issues into more granular tasks?