Skip to main content
Use tk with Cursor to manage issues directly from your editor.

​
Project Rules

Create a .cursor/rules.md file to give Cursor context about tk: 
# Issue Tracking

This project uses **tk (ticket-rs)** for issue tracking.
Issues are stored as Markdown in `.tickets/`.

## Quick Commands

- `tk ready` - Find work with no blockers
- `tk list` - List all open issues
- `tk create "Title" -t task -p 2` - Create issue
- `tk close <id>` - Complete work
- `tk triage` - AI recommendations
- `tk dep add <blocked> <blocker>` - Add dependency

## Issue Format

Issues are Markdown files with YAML frontmatter:

\`\`\`markdown
---
status: open
type: feature
priority: 1
deps: [tk-abc123]
labels: [backend]
---
# Issue Title

Description here.
\`\`\`

## Status Values

- `open` - Ready to be worked on
- `in_progress` - Currently being worked on
- `blocked` - Waiting on dependencies
- `closed` - Completed

## Priority Levels

- P0 - Critical
- P1 - High
- P2 - Medium (default)
- P3 - Low
- P4 - Lowest

​
MCP Integration

Install the ticket-mcp MCP server to give Cursor full access to your issues:

Install MCP Server

One-click install for Cursor. Requires uv installed.
Add to ~/.cursor/mcp.json or .cursor/mcp.json:
{
  "mcpServers": {
    "ticket-mcp": {
      "command": "uvx",
      "args": [
        "ticket-mcp"
      ],
      "env": {}
    }
  }
}
This gives Cursor’s AI direct access to create, update, and manage your issues.

​
Workflow Tips

​
Starting a Session

Ask Cursor: “Run tk ready and show me what I should work on”

​
Creating Issues

Ask Cursor: “Create a bug for the login timeout issue, priority 0”

​
Closing Work

Ask Cursor: “Close tk-abc123, I just fixed it”

​
Checking Health

Ask Cursor: “Run tk doctor and tell me if anything needs fixing”

​
Next Steps

CLI Reference

Full command documentation.

MCP Server

Documentation MCP server setup.