Linear MCP 41c6f275

MCP开发工具

提供方 Goldcap

开发工具 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude
查看接入方式

一个简单的模型上下文协议(MCP)服务器,用于Linear问题管理,支持问题创建、搜索、更新和评论等功能。

一句话选型结论

按资料字段整理

Linear MCP 41c6f275 属于开发工具类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 8 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量8暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

问题管理Python本地部署Linear集成开发工具API服务

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
uvx --from git+https://github.com/Goldcap/linear-mcp.git linear-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Python,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 8 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 8 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Linear MCP 41c6f275当前 8 stdio · 本地进程 本地部署 有 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Goldcap上游标注的维护方 Goldcap
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

9.7 KB
来自项目仓库与上游目录的原文,未做删改

Linear MCP Server

A simple MCP (Model Context Protocol) server for Linear issue management.

Features

  • list_organizations() - List all configured Linear organizations
  • create_issue(title, team_key, description, priority, state_name, assignee_email, organization) - Create a new issue
  • get_issue(identifier, organization) - Get issue by identifier (e.g., "SRE-152")
  • search_issues(query, team_key, state_name, assignee_email, limit, organization) - Search issues with filters
  • list_teams(organization) - List all teams with their workflow states
  • update_issue_status(identifier, state_name, organization) - Change issue status
  • update_issue(identifier, title, description, priority, assignee_email, organization) - Update issue fields
  • add_comment(identifier, body, organization) - Add a comment to an issue

All tools take an organization parameter.

It is optional only when the target is unambiguous — i.e. you configured a single
LINEAR_API_KEY, or exactly one LINEAR_API_KEY_ORGNAME. When several organizations are
configured you must name one
, and a call that omits it fails with an error listing the
choices.

That is deliberate. The server used to fall back to the first key in alphabetical order, so a
write meant for one workspace could land in another's — successfully, with nothing in the
response to show where it went. Guessing a tenant is worse than failing, so it now fails.

Write tools (create_issue, update_issue, update_issue_status, add_comment,
create_project) also echo the resolved workspace back as organization in their result, so a
mis-targeted write is visible rather than silent.

Installation

Using uvx (recommended)```bash

uvx --from git+https://github.com/Goldcap/linear-mcp.git linear-mcp


### Using pip```bash
pip install git+https://github.com/Goldcap/linear-mcp.git

Configuration

Single Organization

Add to your .mcp.json:```json
{
"mcpServers": {
"linear": {
"command": "uvx",
"args": ["--from", "git+https://github.com/Goldcap/linear-mcp.git", "linear-mcp"],
"env": {
"LINEAR_API_KEY": "lin_api_your_key_here"
}
}
}
}


### Multiple Organizations

To work with multiple Linear organizations, use organization-specific environment variables:```json
{
  "mcpServers": {
    "linear": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/Goldcap/linear-mcp.git", "linear-mcp"],
      "env": {
        "LINEAR_API_KEY_APPSUMO": "lin_api_appsumo_key_here",
        "LINEAR_API_KEY_TECHNO87": "lin_api_techno87_key_here"
      }
    }
  }
}

The organization name is extracted from the environment variable name (e.g., LINEAR_API_KEY_APPSUMO → organization name: "appsumo").

With more than one organization configured, every call must name its target:```python
create_issue(title="...", team_key="ENG", organization="koard") # explicit -> fine
create_issue(title="...", team_key="ENG") # raises ValueError


A partial name resolves only when it matches exactly one organization (`"appsumo"` →
`appsumo-production`); a prefix matching several (`"acme"` → `acme-prod`, `acme-staging`) is an
error rather than a coin flip.

You can also mix both formats:```json
{
  "mcpServers": {
    "linear": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/Goldcap/linear-mcp.git", "linear-mcp"],
      "env": {
        "LINEAR_API_KEY": "lin_api_default_key_here",
        "LINEAR_API_KEY_COMPANY_A": "lin_api_company_a_key_here",
        "LINEAR_API_KEY_COMPANY_B": "lin_api_company_b_key_here"
      }
    }
  }
}

Keeping keys out of the config file

Every LINEAR_API_KEY* variable above can be supplied three ways. The first
one that yields a value wins:

Order Source Config holds
1 The variable itself, e.g. LINEAR_API_KEY_KOARD the key
2 A helper command, LINEAR_API_KEY_KOARD_CMD a command
3 The OS keyring, service linear-mcp, username LINEAR_API_KEY_KOARD nothing

Helper commands are the recommended option. The command's stdout (stripped)
becomes the key, so the secret is never written to the config file and never
enters the process environment — it exists only in the server's memory. Only the
command shows up in /proc//environ.```json
{
"mcpServers": {
"linear": {
"command": "uvx",
"args": ["--from", "git+https://github.com/Goldcap/linear-mcp.git", "linear-mcp"],
"env": {
"LINEAR_API_KEY_APPSUMO_CMD": "secret-tool lookup service linear-mcp account appsumo",
"LINEAR_API_KEY_KOARD_CMD": "secret-tool lookup service linear-mcp account koard"
}
}
}
}


Store the keys once with libsecret (GNOME Keyring, KDE Wallet):```bash
secret-tool store --label='Linear MCP (koard)' service linear-mcp account koard

Any command works — pass show linear/koard, op read op://Private/Linear/credential,
or, if you want an audit trail on every secret read:```bash
aws ssm get-parameter --name /koard/linear/api-key --with-decryption \
--query Parameter.Value --output text


**OS keyring** (option 3) needs the optional dependency:```bash
uvx --from "git+https://github.com/Goldcap/linear-mcp.git[keyring]" linear-mcp
keyring set linear-mcp LINEAR_API_KEY_KOARD

Notes:

  • Helper commands run through the shell, so pipes and redirection work. They are
    your own config, but treat the string as executed code.
  • Resolution is cached per process — a rotated key needs a server restart.
  • A helper that fails or prints nothing logs to stderr and that organization is
    skipped; other organizations still load.
  • Plain environment variables keep working unchanged, which is usually what you
    want in CI.

Getting a Linear API Key

  1. Go to Linear Settings → API → Personal API keys
  2. Create a new API key with appropriate scopes
  3. Copy the key (starts with lin_api_)

Note that a personal API key is a long-lived shared credential however it is
stored. The options above reduce where it sits at rest; they do not make it
expire.

Usage Examples

Single Organization

Once configured, Claude Code can:```

Create a new issue

create_issue(title="Fix DNS cleanup", team_key="SRE", description="Need to clean up old DNS records")

Get an issue

get_issue("SRE-152")

Search for issues

search_issues(query="DNS cleanup", team_key="SRE")

Update issue status

update_issue_status("SRE-152", "Done")

Add a comment

add_comment("SRE-152", "Completed the DNS cleanup!")


### Multiple Organizations

When you have multiple organizations configured, you can specify which one to use:```
# List configured organizations
list_organizations()

# Create an issue in Appsumo organization
create_issue(title="Bug in checkout", team_key="ENG", organization="Appsumo")

# Get an issue from Appsumo organization
get_issue("PROD-123", organization="Appsumo")

# Search issues in Techno87 organization
search_issues(query="bug fix", organization="Techno87")

# Update issue in specific organization
update_issue_status("PROD-123", "Done", organization="Appsumo")

# Add comment to issue in specific organization
add_comment("PROD-123", "Fixed the issue!", organization="Techno87")

You can also use natural language to reference organizations:```
"Add a Linear ticket to Appsumo"
"Read a Linear ticket from Techno87"
"Create an issue in Techno87 for the API bug"
"Update the status of SRE-152 in Appsumo to Done"


The organization name matching is case-insensitive and flexible:
- "Appsumo", "appsumo", "APPSUMO" all work
- Spaces and hyphens are ignored for matching

### Labels

`list_labels` shows what exists; `create_issue` and `update_issue` take a
`labels` list of names, matched case-insensitively.```python
list_labels(team_key="KRD", organization="koard")

create_issue(
    title="Telemetry scrubbing audit",
    team_key="KRD",
    labels=["Security", "PCI"],
    organization="koard",
)

# adds Security, keeping labels the issue already has
update_issue("KRD-123", labels=["Security"], organization="koard")

# replaces every label with exactly this list
update_issue("KRD-123", labels=["Security"], replace_labels=True, organization="koard")

Two behaviours worth knowing:

  • Unknown names are an error, not a new label. A typo returns the list of
    names that didn't match rather than quietly creating them. Pass
    create_missing_labels=True when you do want them created.
  • update_issue adds by default. Linear's underlying labelIds field
    replaces the whole set, so adding is done by merging with the issue's current
    labels first. Use replace_labels=True for the raw replace.

Where a team label and a workspace label share a name, the team's own label
wins — matching what the Linear UI would apply to an issue on that team.

Development```bash

git clone https://github.com/Goldcap/linear-mcp.git
cd linear-mcp
pip install -e .
LINEAR_API_KEY=lin_api_xxx linear-mcp


### ⚠️ Bump the version when you change the code

If your MCP client launches this server with `uvx --from /path/to/linear-mcp linear-mcp`,
**uv caches the built wheel against the path and the version in `pyproject.toml`.** Pulling
new code does not invalidate that cache. Neither does `uvx --reinstall`, and
`uv cache clean linear-mcp` is slow enough to be impractical mid-session.

The failure is silent and easy to misread: the server starts, reports the right
organizations at startup, and answers tool calls — using the *old* code. It looks like a
working server, so a fix appears to have simply not worked.

So: **bump `version` in `pyproject.toml` in the same commit as any behaviour change.**

Alternatively, launch it from the working tree instead, which never caches:```json
{ "command": "uv", "args": ["run", "--directory", "/path/to/linear-mcp", "linear-mcp"] }

License

MIT

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Linear MCP 41c6f275 怎么安装?

在客户端按下面的安装命令接入:uvx --from git+https://github.com/Goldcap/linear-mcp.git linear-mcp。装完在客户端配置里引用同一个包或端点。

Linear MCP 41c6f275 怎么在 Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Linear MCP 41c6f275 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Linear MCP 41c6f275 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Linear MCP 41c6f275 支持哪些客户端?

资料标注支持 Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Linear MCP 41c6f275 能提供哪些能力?

资料显示约 8 个工具;能力标签包括 问题管理、开发工具、Python、Claude、API集成。具体工具清单以官方文档为准。

Linear MCP 41c6f275 需要什么运行环境?

运行时为 Python;属于本地进程,需要在本机装好运行环境。

Linear MCP 41c6f275 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。