Ticket AI MCP Server

Ticket AI is an MCP integration. Measures tickets against the ones your team already shipped: sections, length, labels, duplicates.

Packages and local setup

The published pypi package is ticket-ai-mcp, version 0.1.1. Its declared MCP transport is stdio.

The package declares TICKET_AI_TRACKER (required): Which tracker to read: gitlab, jira or github.; TICKET_AI_PROJECT (required): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.