MCP.Market

Ticket AI MCP server

by syrian963·io.github.syrian963/ticket-ai-mcp·v0.1.1
No reviews yet

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

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars18 downloads/wk

Reviews

Write one

Nobody has reviewed Ticket AI yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Ticket AI tools (8, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • house_style

    What this team's tickets look like: template, length, labels, habits.

  • learn_conventions

    Learn how this team writes tickets, and cache the result.

  • review_draft

    Check a ticket you have written but not created yet.

  • review_open_tickets

    Review every open ticket and list them least-aligned first.

  • review_ticket

    Measure one ticket against the learned house style.

  • template_gaps

    Compare the issue template this repository declares with the tickets it gets.

  • ticket_contextwrite action

    Gather what is known about a subject before you write the ticket for it.

  • ticket_template

    The skeleton to fill in when writing a new ticket here.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • Code scan30 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 32 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Ticket AI compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,243 servers
Tools
8
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
18
more than 5% of 12,306 servers with a package

What its tools let an agent do: 7 read · 1 change

Install Ticket AI in Claude Code, Cursor or VS Code

claude mcp add ticket-ai-mcp -- uvx ticket-ai-mcp
Add to Cursor

What the publisher says

From the Ticket AI repository's README, as published. We do not edit it. Read it on GitHub

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 →

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. TICKETAIGITLAB_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 TICKETAICACHE_DIR if you set one and to .ticket-ai/ otherwise, so it happens once rather than once per review.

Then the rest:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Ticket AI: common questions

Is Ticket AI MCP server safe?
Mostly: it is graded B (78/100). Read the Ticket AI safety report
How do I install Ticket AI?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Ticket AI need an API key?
Yes. The registry entry asks for TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN.
Is Ticket AI maintained?
The last commit was 54 days ago (2026-09-12). The latest release is v0.1.1.
How does Ticket AI compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,243 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.