Ticket AI runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 12 Sep 2026.
Measures tickets against the ones your team already shipped: sections, length, labels, duplicates.
We read the source, 1 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.Popen(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add ticket-ai-mcp -- uvx ticket-ai-mcp
{
"mcpServers": {
"ticket-ai-mcp": {
"args": [
"ticket-ai-mcp"
],
"command": "uvx"
}
}
}
[mcp_servers.ticket-ai-mcp]
command = "uvx"
args = ["ticket-ai-mcp"]
{
"mcpServers": {
"ticket-ai-mcp": {
"args": [
"ticket-ai-mcp"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"ticket-ai-mcp": {
"args": [
"ticket-ai-mcp"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
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.), TICKET_AI_GITLAB_TOKEN (GitLab personal access token. The read_api scope is enough; nothing here writes.), 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_JIRA_TOKEN (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 (GitHub token with read access to the repository's issues.), 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.).
The author declared them in the registry entry; get the values from the project itself.
Give your agents your team's real data — read the shared graph, propose actions your team approves.
Your AI sees the screen but can't measure it — measured web UI findings, shared live sessions
Analyze your MCP setup: token costs, grades, duplicates, and optimization tips
ASO Scanner — the free Agent Readiness scanner as an MCP server. Measures your ASO Score (Agent.
Agent Readiness MCP — the free Agent Readiness scanner as an MCP server. Measures your ASO Score.
Catches your AI coding agent when it games the tests - locked-test hashes, tamper detection.
Measures the cost, tokens and duration of a completed agent workflow from its session log.
Read-only access to your Brickway LEGO and alt-brick collection: sets, builds, figures, catalog.
Answers built from our own checks of this server.