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.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Ticket AI. Follow https://mcp.popnx.com/i/syrian963-ticket-ai-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Ticket AI key (create it on the maker’s site) · 3 setting(s) to fill in (TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Ticket AI for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Ticket AI tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
TICKET_AI_TRACKER Which tracker to read: gitlab, jira or github.TICKET_AI_PROJECT The project to measure. A GitLab path like acme/shop or its numeric id, a Jira project key like PROJ, or a 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.Descriptions are as written by the maker.
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"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Ticket AI and tell me what you can do for me, then show me one thing✓ If Claude says it is using Ticket AI or shows a Ticket AI tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
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 Force the language tickets should be written in, overriding what was measured in the corpus. Leave unset unless the board is mid-switch: a measurement beats a setting.TICKET_AI_CACHE_DIR Where the learned profile is kept between runs. Defaults to .ticket-ai/ under the working directory.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Ticket AI yet
Ticket AI runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Ticket AI
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Ticket AI key (create it on the maker’s site) · 3 setting(s) to fill in (TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL) · Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Ticket AI for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Ticket AI tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
TICKET_AI_TRACKER Which tracker to read: gitlab, jira or github.TICKET_AI_PROJECT The project to measure. A GitLab path like acme/shop or its numeric id, a Jira project key like PROJ, or a 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.Descriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open 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-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Ticket AI listed as connected
Use Ticket AI and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Ticket AI or shows a Ticket AI tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
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 Force the language tickets should be written in, overriding what was measured in the corpus. Leave unset unless the board is mid-switch: a measurement beats a setting.TICKET_AI_CACHE_DIR Where the learned profile is kept between runs. Defaults to .ticket-ai/ under the working directory.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Ticket AI key (create it on the maker’s site) · 3 setting(s) to fill in (TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL) · Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Ticket AI for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Ticket AI tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
TICKET_AI_TRACKER Which tracker to read: gitlab, jira or github.TICKET_AI_PROJECT The project to measure. A GitLab path like acme/shop or its numeric id, a Jira project key like PROJ, or a 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.Descriptions are as written by the maker.
In the Ticket AI settings, TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Ticket AI and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Ticket AI or shows a Ticket AI tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
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 Force the language tickets should be written in, overriding what was measured in the corpus. Leave unset unless the board is mid-switch: a measurement beats a setting.TICKET_AI_CACHE_DIR Where the learned profile is kept between runs. Defaults to .ticket-ai/ under the working directory.Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Ticket AI key (create it on the maker’s site) · 3 setting(s) to fill in (TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL) · Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Ticket AI for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Ticket AI tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
TICKET_AI_TRACKER Which tracker to read: gitlab, jira or github.TICKET_AI_PROJECT The project to measure. A GitLab path like acme/shop or its numeric id, a Jira project key like PROJ, or a 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.Descriptions are as written by the maker.
In the Ticket AI settings, TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Ticket AI and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Ticket AI or shows a Ticket AI tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
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 Force the language tickets should be written in, overriding what was measured in the corpus. Leave unset unless the board is mid-switch: a measurement beats a setting.TICKET_AI_CACHE_DIR Where the learned profile is kept between runs. Defaults to .ticket-ai/ under the working directory.Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
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 required envTICKET_AI_PROJECT required envTICKET_AI_GITLAB_URL required envTICKET_AI_GITLAB_TOKEN secret required envTICKET_AI_JIRA_URL envTICKET_AI_JIRA_EMAIL envTICKET_AI_JIRA_TOKEN secret required envTICKET_AI_GITHUB_TOKEN secret required envTICKET_AI_REPO envTICKET_AI_TICKET_LANGUAGE envTICKET_AI_CACHE_DIR envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
pypi: ticket-ai-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account syrian963, which owns the repo
Code last changed 2 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for ticket-ai-mcp@0.1.1
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/syrian963-ticket-ai-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 months ago, and the latest version (0.1.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
| This one Ticket AI | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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