World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Measures tickets against the ones your team already shipped: sections, length, labels, duplicates.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 7/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Ticket AI。按照 https://mcp.popnx.com/i/syrian963-ticket-ai-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要 Ticket AI 的密钥(在开发者网站创建) · 需要填写 3 项设置(TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL) · 需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Ticket AI,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "ticket-ai": { "command": "uvx", "args": [ "ticket-ai-mcp" ], "env": { "TICKET_AI_TRACKER": "your-value", "TICKET_AI_PROJECT": "your-value", "TICKET_AI_GITLAB_URL": "your-value", "TICKET_AI_GITLAB_TOKEN": "your-value", "TICKET_AI_JIRA_TOKEN": "your-value", "TICKET_AI_GITHUB_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Ticket AI 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
TICKET_AI_TRACKER 选择要读取的跟踪器:gitlab、jira 或 github TICKET_AI_PROJECT 要统计的项目。可以是 GitLab 路径(如 acme/shop)或其数字 ID、Jira 项目键(如 PROJ),或 GitHub 的 owner/repo。 TICKET_AI_GITLAB_URL Base URL of the GitLab instance, for example https://gitlab.example.com. Required when the tracker is gitlab.说明为自动翻译,变量名保持原样;不确定时请查看原文。
SettingsDeveloperEdit Config
{
"mcpServers": {
"ticket-ai": {
"command": "uvx",
"args": [
"ticket-ai-mcp"
],
"env": {
"TICKET_AI_TRACKER": "your-value",
"TICKET_AI_PROJECT": "your-value",
"TICKET_AI_GITLAB_URL": "your-value",
"TICKET_AI_GITLAB_TOKEN": "your-value",
"TICKET_AI_JIRA_TOKEN": "your-value",
"TICKET_AI_GITHUB_TOKEN": "your-value"
}
}
}
}只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ticket AI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Ticket AI,或回答中出现 Ticket AI 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
TICKET_AI_JIRA_URL Base URL of the Jira instance. Cloud or self-hosted Server and Data Center; which one is detected from the instance.TICKET_AI_JIRA_EMAIL Account email, for Jira Cloud's basic auth. Leave unset for a public board or for a Server personal access token.TICKET_AI_REPO Checkout to search when gathering context for a subject. Defaults to the working directory, which on a wrong guess produces confident nonsense - the report names the directory it searched.TICKET_AI_TICKET_LANGUAGE 强制指定工单应使用的语言,覆盖从语料库中测得的结果。除非看板正在切换语言,否则请留空:实测结果优先于设置。 TICKET_AI_CACHE_DIR 学习到的配置文件在两次运行之间保存的位置。默认为工作目录下的 .ticket-ai/。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Ticket AI
Ticket AI 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Ticket AI 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要 Ticket AI 的密钥(在开发者网站创建) · 需要填写 3 项设置(TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Ticket AI,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user ticket-ai --env TICKET_AI_TRACKER=your-value --env TICKET_AI_PROJECT=your-value --env TICKET_AI_GITLAB_URL=your-value --env TICKET_AI_GITLAB_TOKEN=your-value --env TICKET_AI_JIRA_TOKEN=your-value --env TICKET_AI_GITHUB_TOKEN=your-value -- uvx ticket-ai-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Ticket AI 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
TICKET_AI_TRACKER 选择要读取的跟踪器:gitlab、jira 或 github TICKET_AI_PROJECT 要统计的项目。可以是 GitLab 路径(如 acme/shop)或其数字 ID、Jira 项目键(如 PROJ),或 GitHub 的 owner/repo。 TICKET_AI_GITLAB_URL Base URL of the GitLab instance, for example https://gitlab.example.com. Required when the tracker is gitlab.说明为自动翻译,变量名保持原样;不确定时请查看原文。
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user ticket-ai --env TICKET_AI_TRACKER=your-value --env TICKET_AI_PROJECT=your-value --env TICKET_AI_GITLAB_URL=your-value --env TICKET_AI_GITLAB_TOKEN=your-value --env TICKET_AI_JIRA_TOKEN=your-value --env TICKET_AI_GITHUB_TOKEN=your-value -- uvx ticket-ai-mcp按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Ticket AI 在列表中并显示已连接
用 Ticket AI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Ticket AI,或回答中出现 Ticket AI 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
TICKET_AI_JIRA_URL Base URL of the Jira instance. Cloud or self-hosted Server and Data Center; which one is detected from the instance.TICKET_AI_JIRA_EMAIL Account email, for Jira Cloud's basic auth. Leave unset for a public board or for a Server personal access token.TICKET_AI_REPO Checkout to search when gathering context for a subject. Defaults to the working directory, which on a wrong guess produces confident nonsense - the report names the directory it searched.TICKET_AI_TICKET_LANGUAGE 强制指定工单应使用的语言,覆盖从语料库中测得的结果。除非看板正在切换语言,否则请留空:实测结果优先于设置。 TICKET_AI_CACHE_DIR 学习到的配置文件在两次运行之间保存的位置。默认为工作目录下的 .ticket-ai/。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 Ticket AI 的密钥(在开发者网站创建) · 需要填写 3 项设置(TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Ticket AI,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "ticket-ai": { "command": "uvx", "args": [ "ticket-ai-mcp" ], "env": { "TICKET_AI_TRACKER": "your-value", "TICKET_AI_PROJECT": "your-value", "TICKET_AI_GITLAB_URL": "your-value", "TICKET_AI_GITLAB_TOKEN": "your-value", "TICKET_AI_JIRA_TOKEN": "your-value", "TICKET_AI_GITHUB_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Ticket AI 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
TICKET_AI_TRACKER 选择要读取的跟踪器:gitlab、jira 或 github TICKET_AI_PROJECT 要统计的项目。可以是 GitLab 路径(如 acme/shop)或其数字 ID、Jira 项目键(如 PROJ),或 GitHub 的 owner/repo。 TICKET_AI_GITLAB_URL Base URL of the GitLab instance, for example https://gitlab.example.com. Required when the tracker is gitlab.说明为自动翻译,变量名保持原样;不确定时请查看原文。
在 Ticket AI 的设置中,TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ticket AI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Ticket AI,或回答中出现 Ticket AI 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
TICKET_AI_JIRA_URL Base URL of the Jira instance. Cloud or self-hosted Server and Data Center; which one is detected from the instance.TICKET_AI_JIRA_EMAIL Account email, for Jira Cloud's basic auth. Leave unset for a public board or for a Server personal access token.TICKET_AI_REPO Checkout to search when gathering context for a subject. Defaults to the working directory, which on a wrong guess produces confident nonsense - the report names the directory it searched.TICKET_AI_TICKET_LANGUAGE 强制指定工单应使用的语言,覆盖从语料库中测得的结果。除非看板正在切换语言,否则请留空:实测结果优先于设置。 TICKET_AI_CACHE_DIR 学习到的配置文件在两次运行之间保存的位置。默认为工作目录下的 .ticket-ai/。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 Ticket AI 的密钥(在开发者网站创建) · 需要填写 3 项设置(TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Ticket AI,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "ticket-ai": { "type": "stdio", "command": "uvx", "args": [ "ticket-ai-mcp" ], "env": { "TICKET_AI_TRACKER": "your-value", "TICKET_AI_PROJECT": "your-value", "TICKET_AI_GITLAB_URL": "your-value", "TICKET_AI_GITLAB_TOKEN": "your-value", "TICKET_AI_JIRA_TOKEN": "your-value", "TICKET_AI_GITHUB_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Ticket AI 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
TICKET_AI_TRACKER 选择要读取的跟踪器:gitlab、jira 或 github TICKET_AI_PROJECT 要统计的项目。可以是 GitLab 路径(如 acme/shop)或其数字 ID、Jira 项目键(如 PROJ),或 GitHub 的 owner/repo。 TICKET_AI_GITLAB_URL Base URL of the GitLab instance, for example https://gitlab.example.com. Required when the tracker is gitlab.说明为自动翻译,变量名保持原样;不确定时请查看原文。
在 Ticket AI 的设置中,TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ticket AI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Ticket AI,或回答中出现 Ticket AI 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
TICKET_AI_JIRA_URL Base URL of the Jira instance. Cloud or self-hosted Server and Data Center; which one is detected from the instance.TICKET_AI_JIRA_EMAIL Account email, for Jira Cloud's basic auth. Leave unset for a public board or for a Server personal access token.TICKET_AI_REPO Checkout to search when gathering context for a subject. Defaults to the working directory, which on a wrong guess produces confident nonsense - the report names the directory it searched.TICKET_AI_TICKET_LANGUAGE 强制指定工单应使用的语言,覆盖从语料库中测得的结果。除非看板正在切换语言,否则请留空:实测结果优先于设置。 TICKET_AI_CACHE_DIR 学习到的配置文件在两次运行之间保存的位置。默认为工作目录下的 .ticket-ai/。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user ticket-ai --env TICKET_AI_TRACKER=your-value --env TICKET_AI_PROJECT=your-value --env TICKET_AI_GITLAB_URL=your-value --env TICKET_AI_GITLAB_TOKEN=your-value --env TICKET_AI_JIRA_TOKEN=your-value --env TICKET_AI_GITHUB_TOKEN=your-value -- uvx ticket-ai-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"ticket-ai": {
"command": "uvx",
"args": [
"ticket-ai-mcp"
],
"env": {
"TICKET_AI_TRACKER": "your-value",
"TICKET_AI_PROJECT": "your-value",
"TICKET_AI_GITLAB_URL": "your-value",
"TICKET_AI_GITLAB_TOKEN": "your-value",
"TICKET_AI_JIRA_TOKEN": "your-value",
"TICKET_AI_GITHUB_TOKEN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ticket-ai": {
"command": "uvx",
"args": [
"ticket-ai-mcp"
],
"env": {
"TICKET_AI_TRACKER": "your-value",
"TICKET_AI_PROJECT": "your-value",
"TICKET_AI_GITLAB_URL": "your-value",
"TICKET_AI_GITLAB_TOKEN": "your-value",
"TICKET_AI_JIRA_TOKEN": "your-value",
"TICKET_AI_GITHUB_TOKEN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"ticket-ai": {
"type": "stdio",
"command": "uvx",
"args": [
"ticket-ai-mcp"
],
"env": {
"TICKET_AI_TRACKER": "your-value",
"TICKET_AI_PROJECT": "your-value",
"TICKET_AI_GITLAB_URL": "your-value",
"TICKET_AI_GITLAB_TOKEN": "your-value",
"TICKET_AI_JIRA_TOKEN": "your-value",
"TICKET_AI_GITHUB_TOKEN": "your-value"
}
}
}
}TICKET_AI_TRACKER 必填 envTICKET_AI_PROJECT 必填 envTICKET_AI_GITLAB_URL 必填 envTICKET_AI_GITLAB_TOKEN 机密 必填 envTICKET_AI_JIRA_URL envTICKET_AI_JIRA_EMAIL envTICKET_AI_JIRA_TOKEN 机密 必填 envTICKET_AI_GITHUB_TOKEN 机密 必填 envTICKET_AI_REPO envTICKET_AI_TICKET_LANGUAGE envTICKET_AI_CACHE_DIR env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 syrian963 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 ticket-ai-mcp@0.1.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/syrian963-ticket-ai-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(0.1.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Ticket AI | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP server and CLI that measures how your team actually writes tickets, and holds new ones to that. Not *this ticket is bad* — *31 of the 40 tickets that shipped here have an acceptance-criteria section, and this one does not.*
No 'Akzeptanzkriterien' section.
31 of the 40 exemplar tickets (78%) have one.
Most ticket advice is free and therefore ignored. "Add acceptance criteria", "include steps to reproduce" — everyone has heard it, nobody changed anything. A count of what already happened in your own project is harder to wave away, and it is not an opinion about tickets.
There is no model in the loop for any of that. Learning the house style, finding related tickets and measuring a draft are counting, and run with no key and no network beyond your tracker. Writing a ticket needs a model, so that part is opt-in and which one is your choice. [What it found when it was run against real boards →](docs/thirty-boards.md)
uv tool install ticket-ai-mcp
Configuration is environment variables only — a token passed as --token ends up in your shell history and in the process list.
export TICKET_AI_TRACKER=gitlab
export TICKET_AI_PROJECT=acme/shop # or the numeric id export TICKET_AI_GITLAB_URL=https://gitlab.example.com export TICKET_AI_GITLAB_TOKEN=... # read_api scope is enough
The token is optional on a public project. TICKET_AI_GITLAB_URL=https://gitlab.com with no token reads any public board, which is the quickest way to see what this does before pointing it at your own instance.
Jira and GitHub
# Jira — Cloud or self-hosted Server / Data Center. Which one you are on is
export TICKET_AI_TRACKER=jira export TICKET_AI_PROJECT=PROJ export TICKET_AI_JIRA_URL=https://acme.atlassian.net
export TICKET_AI_JIRA_EMAIL=you@example.com export TICKET_AI_JIRA_TOKEN=...
export TICKET_AI_JIRA_TOKEN=...
export TICKET_AI_JIRA_API=server
export TICKET_AI_TRACKER=github export TICKET_AI_PROJECT=acme/shop export TICKET_AI_GITHUB_TOKEN=...
mcp-name: io.github.syrian963/ticket-ai-mcp
ticket-ai learn # mine the tracker, cache the profile
ticket-ai style # what it learned
learn takes a minute or two: ranking needs each ticket's comments and linked merge requests, which is an extra request or two per ticket. It caches to TICKET_AI_CACHE_DIR if you set one and to .ticket-ai/ otherwise, so it happens once rather than once per review.
Then the rest:
ticket-ai learn --from '#412,#98' # or name the good ones yourself
ticket-ai context 'export is broken on mobile' # what already exists ticket-ai gaps # declared template vs what arrives ticket-ai draft --title '...' --file draft.md # check one before creating it ticket-ai review '#42' # measure one that exists ticket-ai open # every open ticket, worst first
draft is the one worth building a habit around. Checking a ticket after you create it puts the review past the point of no return: the board has already been notified and every fix is now an edit with a history.
$ ticket-ai draft --title 'Filter kaputt' --file draft.md
Alignment with house style: 33% over 3 checks
The shortest quarter of tickets that shipped here start at 639; the median is 1079.
62% of the exemplars are labelled.
--from is taken as given: no filtering, no scoring against your choices. Name a ticket with a three-word description and that is your answer about how this team writes tickets, and the profile will say so.
{
"mcpServers": { "ticket-ai": { "command": "uvx", "args": ["ticket-ai-mcp"], "env": { "TICKET_AI_TRACKER": "gitlab", "TICKET_AI_PROJECT": "acme/shop", "TICKET_AI_GITLAB_URL": "https://gitlab.example.com", "TICKET_AI_GITLAB_TOKEN": "..." } } } }
Eight tools, all read-only: learn_conventions, house_style, ticket_template, ticket_context, template_gaps, review_draft, review_ticket, review_open_tickets.
Add TICKET_AI_REPO to the env block if the checkout you want searched is not the assistant's working directory.
The path to reach for if you already use Claude Code: no key, no compose, no second model call. Ask for a ticket and the assistant does five things, three of them here:
ticket_context runs a text search, not an analysis; it says where to look, it does not save you looking.Counting cannot produce a paragraph of German, so writing a ticket needs a model. Everything else needs nothing.
| Writes | Needs | |
|---|---|---|
| MCP, in Claude Code | yes | nothing — the assistant is already a model |
| `--writer ollama` | yes | a model on your machine. No key, no account, nothing leaves the laptop |
| `--writer openai` | yes | a base URL and a key. OpenRouter, Azure AI Foundry, vLLM, any provider |
| no writer (default) | no | nothing. Measures and gathers; you write |
export TICKET_AI_WRITER=ollama # or openai, with a base url and key
ticket-ai models # what that endpoint can reach ticket-ai compose --title 'Etikettendruck bricht bei mehr als zehn Positionen ab' ticket-ai models --workflow # an Actions workflow that drafts new issues
compose writes the body, measures it, hands the findings back to the model once, and prints the review to stderr so the body alone can be redirected. --fail-under makes it refuse to emit a draft that missed the house style.
Whichever model writes, the draft goes through the same measurement as any other ticket. That loop is why a small local model is usable here: it writes into a shape worked out by counting, and is marked against your team's own tickets afterwards.
ticket-ai ui --lang de # or en
A local page on 127.0.0.1:8760 with three tabs: the house style, a box to paste a draft into, and the open backlog worst-first. Loopback only, because this process holds a tracker token, and there is no flag to change that.
No build step and no CDN — one HTML file with its CSS and JavaScript inline.
export TICKET_AI_UI_LANGUAGE=de # buttons and headings
export TICKET_AI_TICKET_LANGUAGE=de # what it says to write tickets in
The distinction is easy to collapse and worth keeping. A German team may want the tool's own buttons in English; someone joining a German board still has to write the ticket in German.
TICKET_AI_TICKET_LANGUAGE overrides what the corpus measured and takes effect without re-learning. Leave it unset unless the board is mid-switch — a measurement beats a setting, and forcing a language the board does not use makes every existing ticket fail the language check.
Findings, the caveats under them and the list of what a ticket already got right are all rendered in the reader's language at the moment they are shown. The section names inside them are not: those are the team's own headings, and translating one turns it into a section the team does not have.
ticket-ai review "$CI_ISSUE" --fail-under 0.5
The house style. Sections, length, labels, title markers, language — over a corpus it either took from you or found itself. Every finding cites a count over that corpus.
The tickets that failed, not only the ones that worked. A rate can be a comparison: not "78% of tickets have acceptance criteria" but *"78% of the ones that shipped, and 30% of the ones that stalled"*. The second is evidence; the first invites a shrug.
The split is on outcome alone — a merged change, a reopen, a run of clarifying questions — and never on what the ticket contains, because splitting on content and then comparing content would be circular. Tickets a staleness bot closed are left out of both groups: those say something about attention rather than about writing. On a board where nothing separates the two, it says so, which is worth knowing before anyone is asked to write differently. [docs/shipped-against-stalled.md](docs/shipped-against-stalled.md) has the guards and the real board that forced the bot exclusion.
Sections that only travel together. A section carried by 41% of tickets is under any threshold worth having — but if it is on 76% of the tickets that also have a *Ziel* section and 20% of the ones that do not, the team has a template and applies it to one kind of work. A board-wide rate hides that entirely.
The form you declared, against the tickets you got. With a .github/ISSUE_TEMPLATE or .gitlab/issue_templates in the checkout, gaps lines each field up against how often tickets actually carry it — and the gap runs both ways. A required field that turns up in 10% of tickets is a form asking for something people cannot easily give. A section most tickets carry that no form mentions is a convention the project grew and never wrote down.
What you need to write one. Give it a subject and it returns the related past tickets, the files the merge requests for those tickets actually changed, and the files in your checkout that mention it. That middle one lives only in the tracker's history — no amount of reading the code produces it, and it is usually the fastest way to find where the work will land.
Only closed tickets are sampled: an open ticket may be beautifully written, but nothing about it yet shows anyone could act on it. Each is scored on
| Signal | Weight | Why |
|---|---|---|
| A merged MR is attached | 0.30 | Strongest evidence someone could build it as written |
| Substantial description | 0.20 | A stub teaches nothing about a template |
| Has sections | 0.15 | The template is the thing being learned |
| No clarifying questions | 0.15 | Eleven "what do you mean?" comments means it was not clear |
| Never reopened | 0.10 | Reopened means closed before it was understood |
| Labelled | 0.10 |
Tickets opened and closed inside an hour