Skip to content
mcp/skillhub

Ticket AI MCP Server

by syrian963io.github.syrian963/ticket-ai-mcpv0.1.1

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

0Pythonstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active28d ago

Install Ticket AI MCP server

Install in Claude Code

claude mcp add ticket-ai -e TICKET_AI_TRACKER='<ticket-ai-tracker>' -e TICKET_AI_PROJECT='<ticket-ai-project>' -e TICKET_AI_GITLAB_TOKEN='<ticket-ai-gitlab-token>' -e TICKET_AI_JIRA_TOKEN='<ticket-ai-jira-token>' -e TICKET_AI_GITHUB_TOKEN='<ticket-ai-github-token>' -- uvx ticket-ai-mcp

Configuration

VariableRequiredSecretDescription
TICKET_AI_TRACKERyes—Which tracker to read: gitlab, jira or github.
TICKET_AI_PROJECTyes—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—yesGitLab 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—yesJira 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—yesGitHub 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.

Freshness

Active — last maintenance signal 28d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-09-12 · 28d ago · GitHub

  2. Latest release

    2026-09-11 · 29d ago · GitHub · v0.1.1

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-09-11 · 29d ago · official registry · v0.1.1

FAQ

›How do I install the Ticket AI MCP server in Claude Code?

Run: claude mcp add ticket-ai -e TICKET_AI_TRACKER='<ticket-ai-tracker>' -e TICKET_AI_PROJECT='<ticket-ai-project>' -e TICKET_AI_GITLAB_TOKEN='<ticket-ai-gitlab-token>' -e TICKET_AI_JIRA_TOKEN='<ticket-ai-jira-token>' -e TICKET_AI_GITHUB_TOKEN='<ticket-ai-github-token>' -- uvx ticket-ai-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Ticket AI require an API key?

Yes. It expects TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, of which 3 are secrets.

›Can I use Ticket AI as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Ticket AI in the official MCP registry?

Yes, as io.github.syrian963/ticket-ai-mcp.

Alternatives to Ticket AI

Other project management MCP servers.

View all