tpm-mcp

PROJECT MANAGEMENT (TPM): Get project roadmap showing work status.

USE THIS TOOL WHEN:

• User asks "what's in progress?" or "what are we working on?"

• User asks "TPM status", ":TPM:" prefix, or "show me the roadmap"

• User asks about pending/blocked/completed work

• Starting a work session to see current state

• User completes work and you need to find related tasks to mark done

Returns summary of organizations, projects, and tickets. Use project_id filter to reduce output.

PROJECT MANAGEMENT (TPM): Create a new ticket, epic, or issue to track.

USE THIS TOOL WHEN:

• User says ":TPM: Add X feature to the roadmap"

• User wants to add a new feature/ticket/issue

• User says "add ticket for X" or "create feature for Y"

• Breaking down work into trackable items

• User asks to scope out or define new work

• User discusses new work that should be tracked

Use roadmap_view first to get the project_id. Tickets are high-level work items (like Jira epics/stories).

ID AUTO-GENERATION: IDs are always auto-generated as {PREFIX}-{NNN} (e.g., FEAT-001, ISSUE-042). The number is automatically incremented based on existing tickets with that prefix.

OPTIONAL PREFIX PARAMETER: Provide a prefix to categorize the ticket type:

• FEAT: New features or capabilities

• ISSUE: Bugs, problems, or issues to fix

• TASK: General tasks or chores

• INFRA: Infrastructure or DevOps work

• DOC: Documentation tasks

If no prefix is provided, uses the project ID as the prefix (e.g., FRONTEND-001, BACKEND-042).

PROJECT MANAGEMENT (TPM): Update a ticket's status, priority, or details.

USE THIS TOOL WHEN:

• User says "I just finished implementing X" - mark related ticket as done

• User says "I've pushed commits for X" - update status based on progress

• Marking work as in-progress, done, or blocked

• Changing priority of a ticket

• User completes a ticket and needs to update status

• Adding/updating tags or assignees

Use roadmap_view first to find the ticket_id.

PROJECT MANAGEMENT: List ticket IDs with status/priority. Returns id, status, priority only - use ticket_get for details.

PROJECT MANAGEMENT (TPM): Search tickets by keyword.

USE THIS TOOL WHEN:

• User asks "find tickets about X" or "search for Y"

• Looking for tickets by keywords in title or description

• Need to discover relevant tickets across projects

Searches title and description. Supports prefix matching (e.g., "org" matches "organization"). Case-insensitive. All filters are combinable.

PROJECT MANAGEMENT: Get info about a ticket and its tasks.

IMPORTANT: Do NOT pass detail='full' unless explicitly asked for full/all details. The default 'summary' is sufficient for most queries. Only use 'full' when user specifically asks for implementation details, metadata, or complete task information.

PROJECT MANAGEMENT: Get full details of ONE specific task.

Use this to drill into a single task's implementation details (metadata, files_to_modify, technical_notes). Prefer ticket_get for overview, use this only when you need deep task details.

PROJECT MANAGEMENT (TPM): Create a task (sub-item) under a ticket.

USE THIS TOOL WHEN:

• Breaking down a ticket into smaller tasks

• User asks to add implementation steps

• Creating a work breakdown structure

PROJECT MANAGEMENT (TPM): Update a task's status or details. Use when completing or updating task progress.

PROJECT MANAGEMENT (TPM): List task IDs with status. Returns id, ticket_id, status only - use task_get for details.

PROJECT MANAGEMENT (TPM): Add a note/comment to a ticket or task for context or decisions.

PROJECT MANAGEMENT (TPM): List notes for an entity. Returns id, created_at, preview (first 100 chars). Use note_get for full content.

PROJECT MANAGEMENT (TPM): Get full content of a specific note by ID.

PROJECT MANAGEMENT: List all organizations. Usually only one org exists.

PROJECT MANAGEMENT: Create a new organization (rarely needed).

PROJECT MANAGEMENT: List projects in an organization.

PROJECT MANAGEMENT: Create a new project under an organization.

Get information about the tracker MCP server: database location, stats, and usage.