Ticket AI MCP Server

What this does

Ticket AI exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

TICKET_AI_TRACKER
TICKET_AI_PROJECT
TICKET_AI_GITLAB_URL
TICKET_AI_GITLAB_TOKEN
TICKET_AI_JIRA_URL
TICKET_AI_JIRA_EMAIL
TICKET_AI_JIRA_TOKEN
TICKET_AI_GITHUB_TOKEN
TICKET_AI_REPO
TICKET_AI_TICKET_LANGUAGE
TICKET_AI_CACHE_DIR

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Ticket AI?

Run the Claude Code command in the install section to add Ticket AI to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Ticket AI?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Ticket AI as well.

Does Ticket AI need an API key?

Yes. Before it can run, set these environment variables: TICKET_AI_TRACKER, TICKET_AI_PROJECT, TICKET_AI_GITLAB_URL, TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_URL, TICKET_AI_JIRA_EMAIL, TICKET_AI_JIRA_TOKEN, TICKET_AI_GITHUB_TOKEN, TICKET_AI_REPO, TICKET_AI_TICKET_LANGUAGE, TICKET_AI_CACHE_DIR. They go in the env block of your MCP config.