Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Ticket AI

by syrian963version 0.1.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.syrian963/ticket-ai-mcp

How to install

What it does

Measures tickets against the ones your team already shipped: sections, length, labels, duplicates.

  • Connects Runs on your computer
  • Account or key Needs TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN · 3 settings to fill in (TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL)
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

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

Let AI install it

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.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

    Open the uv download page ↗

    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

  2. Sign up and create a Ticket AI key

    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.

    Open the Ticket AI site ↗

  3. Fill in 3 setting(s)

    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.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "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

  6. Quit Claude and open it again

  7. Try it

    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

5 optional setting(s) (works without them)

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

What you can do instead

A · Use an app that can connect Ticket AI

  • 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
  • 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)
  • 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)
  • 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)

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)

Let AI install it

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.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

    Open the uv download page ↗

    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

  2. Sign up and create a Ticket AI key

    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.

    Open the Ticket AI site ↗

  3. Fill in 3 setting(s)

    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.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    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

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Ticket AI listed as connected

  7. Try it

    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

5 optional setting(s) (works without them)

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)

Let AI install it

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.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

    Open the uv download page ↗

    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

  2. Sign up and create a Ticket AI key

    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.

    Open the Ticket AI site ↗

  3. Fill in 3 setting(s)

    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.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    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

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    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

5 optional setting(s) (works without them)

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)

Let AI install it

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.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

    Open the uv download page ↗

    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

  2. Sign up and create a Ticket AI key

    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.

    Open the Ticket AI site ↗

  3. Fill in 3 setting(s)

    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.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    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

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    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

5 optional setting(s) (works without them)

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

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Ticket AI💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

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-mcp

Claude 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"
      }
    }
  }
}

Values you fill in

  • TICKET_AI_TRACKER required env
    Which tracker to read: gitlab, jira or github.
  • TICKET_AI_PROJECT required env
    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 required env
    Base URL of the GitLab instance, for example https://gitlab.example.com. Required when the tracker is gitlab.
  • TICKET_AI_GITLAB_TOKEN secret required env
    GitLab personal access token. The read_api scope is enough; nothing here writes.
  • TICKET_AI_JIRA_URL env
    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 env
    Account email, for Jira Cloud's basic auth. Leave unset for a public board or for a Server personal access token.
  • TICKET_AI_JIRA_TOKEN secret required env
    Jira API token from id.atlassian.com, or a Server personal access token on its own. Leave unset to read a public instance anonymously.
  • TICKET_AI_GITHUB_TOKEN secret required env
    GitHub token with read access to the repository's issues.
  • TICKET_AI_REPO env
    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 env
    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 env
    Where the learned profile is kept between runs. Defaults to .ticket-ai/ under the working directory.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
16/wk
Connection
Runs on your computer
Latest versioni
0.1.1
Categoryi
Other
Published to registryi
Sep 11, 2026
Code last changedi
Sep 12, 2026
Maker
syrian963
Packages
pypi: ticket-ai-mcp
Website
github.com
Registry status
Active

Which apps can use it

Based 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

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account syrian963, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for ticket-ai-mcp@0.1.1

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/syrian963-ticket-ai-mcp.svg)](https://mcp.popnx.com/en/servers/syrian963-ticket-ai-mcp)

Discussion

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.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20613 servers in this category
  • Published to the registry more recently than 37% of the other 20613 servers in this category
  • Basic checks equal to or better than 99% of the other 20613 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ticket AI safe?

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.

What keys or codes does it need?

You need to fill in: TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

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

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Ticket AI
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

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.

ticket-ai

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)

Install

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

detected from the instance; you do not have to say.

export TICKET_AI_TRACKER=jira export TICKET_AI_PROJECT=PROJ export TICKET_AI_JIRA_URL=https://acme.atlassian.net

Leave the credentials unset for a public board — plenty answer without any.

Cloud: the token comes from id.atlassian.com, and is not the password.

export TICKET_AI_JIRA_EMAIL=you@example.com export TICKET_AI_JIRA_TOKEN=...

Self-hosted: a personal access token on its own, sent as a Bearer.

export TICKET_AI_JIRA_TOKEN=...

Only if detection gets it wrong: cloud | server | auto (the default)

export TICKET_AI_JIRA_API=server

GitHub

export TICKET_AI_TRACKER=github export TICKET_AI_PROJECT=acme/shop export TICKET_AI_GITHUB_TOKEN=...

mcp-name: io.github.syrian963/ticket-ai-mcp

One command

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

MEDIUM - The description is 116 characters.

The shortest quarter of tickets that shipped here start at 639; the median is 1079.

MEDIUM - The ticket has no labels.

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.

As an MCP server

{

"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.

Writing a ticket this way

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:

  1. `ticket_template` — the shape: which sections, how long, what language, which labels.
  2. `ticket_context` — what exists: related tickets, the files their merge requests changed, the files in the checkout that mention it.
  3. It reads those files. ticket_context runs a text search, not an analysis; it says where to look, it does not save you looking.
  4. It writes the ticket.
  5. `review_draft` — measures what it wrote, and fixes what that finds before showing you anything.

Where the "AI" is

Counting cannot produce a paragraph of German, so writing a ticket needs a model. Everything else needs nothing.

WritesNeeds
MCP, in Claude Codeyesnothing — the assistant is already a model
`--writer ollama`yesa model on your machine. No key, no account, nothing leaves the laptop
`--writer openai`yesa base URL and a key. OpenRouter, Azure AI Foundry, vLLM, any provider
no writer (default)nonothing. 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.

A page instead

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.

Two languages, and they are separate
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.

In CI
ticket-ai review "$CI_ISSUE" --fail-under 0.5

What it measures

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.

How the mining works

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

SignalWeightWhy
A merged MR is attached0.30Strongest evidence someone could build it as written
Substantial description0.20A stub teaches nothing about a template
Has sections0.15The template is the thing being learned
No clarifying questions0.15Eleven "what do you mean?" comments means it was not clear
Never reopened0.10Reopened means closed before it was understood
Labelled0.10

Tickets opened and closed inside an hour

Only the beginning is shown; read the rest in the repo