# MCP Request-tracker [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/crunchtools/mcp-request-tracker  
**GitHub Stars:** 0  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-request-tracker

## Description
Secure MCP server for Request Tracker (RT) ticket management

## Tools
Capabilities this server exposes over MCP:

- **search_tickets_tool** — Search for tickets using RT query syntax.
- **get_ticket_tool** — Get details of a specific ticket.
- **get_ticket_history_tool** — Get the history/changelog of a ticket.
- **get_my_open_tickets_tool** — Get all open tickets assigned to a user.
- **get_new_tickets_tool** — Get all new (unassigned) tickets, optionally filtered by queue.
- **set_ticket_owner_tool** — Set the owner of a ticket (take/assign ticket).
- **set_ticket_status_tool** — Set the status of a ticket.
- **update_ticket_tool** — Update ticket fields (subject, priority, queue). All fields are optional.
- **resolve_ticket_tool** — Resolve/close a ticket, optionally adding a comment.
- **open_ticket_tool** — Open a ticket (change status from new to open), optionally taking ownership.
- **take_ticket_tool** — Take ownership of a ticket and open it.
- **set_time_worked_tool** — Set the total time worked on a ticket.
- **add_time_worked_tool** — Add time to the time worked on a ticket.
- **add_ticket_comment_tool** — Add a private comment/note to a ticket (not visible to requestor).
- **reply_to_ticket_tool** — Reply to a ticket (correspondence visible to requestor).
- **create_ticket_tool** — Create a new ticket.
- **complete_weekly_checklist_tool** — Complete a weekly checklist ticket with results.

This is a workflow shortcut that:
1. Takes ownership of the ticket
2. Opens the ticket
3. Adds correspondence with checklist results
4. Adds time worked (if specified)
5. Adds a "Completed" comment
6. Resolves the ticket

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-request-tracker": {
    "command": "uvx",
    "args": ["mcp-request-tracker-crunchtools"],
    "env": {
      "RT_URL": "",
      "RT_USER": "",
      "RT_PASS": ""
    }
  }
}
```

**Requires environment variables:** `RT_URL`, `RT_USER`, `RT_PASS` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What MCP Request-tracker does

MCP Request-tracker exposes Request Tracker ticket operations through the Model Context Protocol. It covers the main stages of an RT workflow: finding tickets, reading ticket details and history, taking or assigning work, changing status, recording time, communicating with requestors, creating tickets, and resolving completed work.

Search uses RT query syntax, including conditions on status, owner, subject, queue, and creation date. The server can also retrieve open tickets assigned to a user and list new, unassigned tickets, with optional queue filtering.

A dedicated weekly checklist operation packages a recurring sequence into one workflow. It takes ownership of the ticket, opens it, adds the checklist results as correspondence, records time when supplied, adds a completion comment, and resolves the ticket.

## How it works

The server connects to an RT instance using its base URL and credentials supplied through environment variables. MCP clients invoke individual ticket tools or the combined checklist workflow. Available operations distinguish between private internal notes and correspondence visible to the requestor, which supports both internal updates and external replies.

Ticket-management tools include ownership changes, status changes, opening, taking, resolving, and field updates for subject, priority, and queue. Time can either be replaced with a total value or increased by an additional amount. Resolution can optionally include a comment, while ticket creation supports opening new work in RT.

The server is designed to avoid exposing credentials in logs or errors. Password values use secret handling, credentials are removed from error messages, and the server does not read or write files or execute shell commands.

## Setup and configuration

Install the package with `uvx mcp-request-tracker-crunchtools` or with pip:

```bash
pip install mcp-request-tracker-crunchtools
```

A container image is also available:

```bash
podman run -e RT_URL=... -e RT_USER=... -e RT_PASS=... quay.io/crunchtools/mcp-request-tracker
```

Set these required variables before starting the server:

- `RT_URL`: the base URL of the RT instance.
- `RT_USER`: the RT username.
- `RT_PASS`: the RT password.

For an RT deployment protected by HTTP Basic Authentication, also set `RT_HTTP_USER` and `RT_HTTP_PASS`.

Claude Code can register the server with `claude mcp add`, passing the RT variables through `--env` and launching the package with `uvx`, or by running the container with standard input enabled. The project also documents development commands for dependency installation, tests, linting, and type checking with `uv`.

## Tools and capabilities

The available tool groups are:

- Search and retrieval: search tickets with RT query syntax, get ticket details, view ticket history, find a user's open tickets, and list new tickets.
- Ticket changes: set an owner, change status, open a ticket, take ownership and open it, update subject, priority, or queue, and resolve a ticket.
- Time tracking: set total time worked or add time to the existing total.
- Communication: add a private comment or send requester-visible correspondence.
- Creation and workflows: create tickets and complete weekly checklist tickets through the combined workflow.

The implementation is intended for Linux, macOS, and Windows, and is licensed under AGPL-3.0.

_Full upstream README: https://allmcps.com/mcp/mcp-request-tracker/readme_