Skip to main content
ticket-rs provides two MCP (Model Context Protocol) servers for AI assistants:
ServerPurposeUse Case
ticket-docsSearch tk documentationHelp AI understand tk commands and features
ticket-mcpFull issue management toolsLet AI agents create, update, and manage issues

ticket-docs (Docs MCP)

The docs MCP server gives AI assistants access to search ticket-rs documentation directly.

Setup

Add to project .mcp.json:
claude mcp add --transport http --scope project ticket-docs https://docs.ticket.rs/mcp
Add --scope user to make it available across all projects.

Available Tools

ToolDescription
search_docsSearch tk documentation for relevant content
Example prompts:
  • “How do I add a dependency between issues?”
  • “What does tk triage show?”
  • “How do I sync with GitHub?”

ticket-mcp (Agentic Tools)

The ticket-mcp package provides full issue management capabilities, allowing AI agents to create, update, and manage issues directly.

Installation

# Recommended: use uv
uv tool install ticket-mcp

# Or with pip
pip install ticket-mcp
Requires Python 3.10+ and the tk binary in PATH. Install tk first: curl -fsSL https://ticket-rs.io/install.sh | bash

Setup

claude mcp add ticket uvx ticket-mcp

Available Tools

Read Operations

ToolDescription
readyGet issues ready to work on (no blocking dependencies)
list_issuesList issues with optional filters
showShow full details for a specific issue
statsGet repository statistics
searchSearch issues using TF-IDF similarity
similarFind issues similar to a given issue

Write Operations

ToolDescription
createCreate a new issue
updateUpdate an existing issue
closeClose an issue
launchMark an issue as in-progress
resolveResolve an issue (close + show unblocked)

Dependency Operations

ToolDescription
dep_addAdd a dependency between issues
dep_removeRemove a dependency between issues
dep_treeShow dependency tree for an issue
dep_cyclesDetect dependency cycles in the graph

AI/Analytics Operations

ToolDescription
triageTHE MEGA-COMMAND: unified recommendations, quick wins, blockers, health
next_actionGet single top recommendation for next action
priorityGet PageRank-based priority recommendations
planGet parallel execution plan (topological sort)
insightsGet graph analytics (PageRank, betweenness, critical path)

Workflow Operations

ToolDescription
primeGet AI workflow context for the repository
validateValidate all issue files
contextSet or show workspace context

Discovery Tools

ToolDescription
discover_toolsList all available tools (saves context)
get_tool_infoGet detailed info for a specific tool

Usage Example

# 1. Set workspace context
context(workspace_root='/path/to/repo', action='set')

# 2. Get AI recommendations
triage()  # Full recommendations with health score
# or
next_action()  # Single top pick for quick decisions

# 3. See what's ready to work on
ready()

# 4. Start work on an issue
launch('tk-123')

# 5. Resolve when done (shows newly unblocked issues)
resolve('tk-123')

Context Engineering

ticket-mcp is optimized for AI agent efficiency:
  • Lazy tool loading: Use discover_tools() first, then get_tool_info() for details
  • Minimal models: List views use ~80% less tokens than full issues
  • Result compaction: Large result sets are automatically compacted
Configure thresholds via environment variables:
TICKET_MCP_COMPACTION_THRESHOLD=20  # Compact results with more than N issues
TICKET_MCP_PREVIEW_COUNT=5          # Show first N issues in preview

Which Should I Use?

Docs MCP

Best for learningUse when you want AI to understand tk commands and answer questions about features.

ticket-mcp

Best for automationUse when you want AI agents to actually manage your issues—create, update, close, etc.
Recommendation: Use both together. The docs server helps AI understand how to use tk, while ticket-mcp lets it take action.

Troubleshooting

Verify the server is configured:
# For Claude Code
claude mcp list
You should see ticket-docs and/or ticket-mcp in the list.
Install the tk binary first:
curl -fsSL https://ticket-rs.io/install.sh | bash
Verify it’s in your PATH:
which tk
tk --version
Make sure you’ve set the workspace context and initialized tickets:
# In your project directory
tk init
tk demo  # Create sample issues to test
The docs MCP server requires internet access to reach docs.ticket.rs. Check your network connection.

Next Steps