Allows an AI client to manage Request Tracker tickets, track time, and automate workflows through search, creation, and updates.
Also known as crunchtools/mcp-request-tracker, mcp-request-tracker, mcp-request-tracker-crunchtools
- Stars
- 0
- Tools
- 16
- Downloads, 30 days
- 759
- Latest version
- 0.1.1
- Last commit
- Nov 14, 2026
- License
- AGPL-3.0
What is Request Tracker MCP?
Request Tracker allows an AI client to manage Request Tracker tickets, track time, and automate workflows through search, creation, and updates. It exposes 16 tools, such as search_tickets, get_ticket, get_ticket_history.
Summary generated from the project's README
About Request Tracker MCP server
Managing Request Tracker tickets through an AI client allows developers and support teams to handle helpdesk workflows directly from their chat interface. This server enables users to search for specific issues using RT query syntax, create new tickets, and update existing ones by changing owners or statuses. It also provides specialized tools for time tracking, such as adding time worked to a ticket, and communication tools like adding private comments or public correspondence.
To set up the server, you must provide your RT_URL, RT_USER, and RT_PASS via environment variables. You can run it locally using uvx or pip on Linux, macOS, and Windows, or deploy it via a Podman container. The implementation prioritizes security by using SecretStr to prevent passwords from being logged and by scrubbing credentials from error messages. It includes pre-built automation like the complete_weekly_checklist tool to streamline repetitive tasks.
What you can do with it
- 1Locating specific support issuesFind all unassigned tickets that match a specific status or queue using query syntax.
- 2Logging billable hoursRecord the amount of time spent working on a specific ticket for reporting.
- 3Automating routine maintenanceExecute a pre-defined workflow to finish a weekly checklist ticket.
- 4Updating ticket lifecycle statusChange the ownership or resolution status of a ticket to keep the queue organized.
Written from the project's README. Every use case is checked against a quote from it.
How to install Request Tracker MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Request Tracker MCP in Claude Code
$ claude mcp add mcp-request-tracker -- uvx mcp-request-tracker-crunchtoolsInstall Request Tracker MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-request-tracker": {
"command": "uvx",
"args": [
"mcp-request-tracker-crunchtools"
]
}
}
}Install Request Tracker MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-request-tracker": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-request-tracker-crunchtools"
]
}
}
}Install Request Tracker MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-request-tracker","type":"stdio","command":"uvx","args":["mcp-request-tracker-crunchtools"]}'Install Request Tracker MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-request-tracker": {
"command": "uvx",
"args": [
"mcp-request-tracker-crunchtools"
]
}
}
}Install Request Tracker MCP in Codex
$ codex mcp add mcp-request-tracker -- uvx mcp-request-tracker-crunchtoolsInstall Request Tracker MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-request-tracker] command = "uvx" args = ["mcp-request-tracker-crunchtools"]
Install Request Tracker MCP in Gemini CLI
$ gemini mcp add -s user mcp-request-tracker uvx -- mcp-request-tracker-crunchtoolsInstall Request Tracker MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-request-tracker": {
"command": "uvx",
"args": [
"mcp-request-tracker-crunchtools"
]
}
}
}Request Tracker MCP tools 16
Detected from the READMEsearch_ticketsget_ticketget_ticket_historyget_my_open_ticketsget_new_ticketsset_ticket_ownerset_ticket_statusopen_ticketresolve_tickettake_ticketset_time_workedadd_time_worked
| search_tickets | — | |
| get_ticket | — | |
| get_ticket_history | — | |
| get_my_open_tickets | — | |
| get_new_tickets | — | |
| set_ticket_owner | — | |
| set_ticket_status | — | |
| open_ticket | — | |
| resolve_ticket | — | |
| take_ticket | — | |
| set_time_worked | — | |
| add_time_worked | — |
Show all 16 toolsShow fewer tools
add_ticket_commentreply_to_ticketcreate_ticketcomplete_weekly_checklist
| add_ticket_comment | — | |
| reply_to_ticket | — | |
| create_ticket | — | |
| complete_weekly_checklist | — |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablecrunchtools/mcp-request-tracker is public and reachablegithub.com/crunchtools/mcp-request-tracker ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Sigstore attestation for mcp-request-tracker-crunchtoolspypi.org/project/mcp-request-tracker-crunchtools/ ↗Pass
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/crunchtools/mcp-request-tracker ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from mcp-request-tracker-crunchtoolsPass
- No critical advisory in the package or its dependencies65 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model16 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMCP Request Tracker CrunchTools
A secure MCP (Model Context Protocol) server for Request Tracker (RT) ticket management.
Features
- Secure Credential Handling: Passwords stored as SecretStr, never logged
- Full Ticket Management: Search, view, create, update, and resolve tickets
- Time Tracking: Track time worked on tickets
- Workflow Automation: Pre-built workflows like checklist completion
- Cross-Platform: Works on Linux, macOS, and Windows
Installation
Option 1: Using uvx (Recommended)
uvx mcp-request-tracker-crunchtools
Option 2: Using pip
pip install mcp-request-tracker-crunchtools
Option 3: Using Container
podman run -e RT_URL=... -e RT_USER=... -e RT_PASS=... quay.io/crunchtools/mcp-request-tracker
Configuration
Set the following environment variables:
| Variable | Required | Description |
|---|---|---|
RT_URL |
Yes | Base URL of your RT server |
RT_USER |
Yes | RT username |
RT_PASS |
Yes | RT password |
RT_HTTP_USER |
No | HTTP Basic Auth username |
RT_HTTP_PASS |
No | HTTP Basic Auth password |
Usage with Claude Code
Using uvx
claude mcp add mcp-request-tracker-crunchtools \
--env RT_URL=https://rt.example.com \
--env RT_USER=your_username \
--env RT_PASS=your_password \
-- uvx mcp-request-tracker-crunchtools
Using Container
claude mcp add mcp-request-tracker-crunchtools \
--env RT_URL=https://rt.example.com \
--env RT_USER=your_username \
--env RT_PASS=your_password \
-- podman run -i --rm -e RT_URL -e RT_USER -e RT_PASS quay.io/crunchtools/mcp-request-tracker
Available Tools
Search and View
search_tickets- Search tickets using RT query syntaxget_ticket- Get ticket detailsget_ticket_history- Get ticket history/changelogget_my_open_tickets- Get open tickets for a userget_new_tickets- Get new/unassigned tickets
Update Tickets
set_ticket_owner- Set ticket ownerset_ticket_status- Set ticket statusopen_ticket- Open a ticketresolve_ticket- Resolve/close a tickettake_ticket- Take ownership and open
Time Tracking
set_time_worked- Set total time workedadd_time_worked- Add time to existing time
Communication
add_ticket_comment- Add private comment (not visible to requestor)reply_to_ticket- Add correspondence (visible to requestor)
Creation
create_ticket- Create a new ticket
Workflows
complete_weekly_checklist- Complete a weekly checklist ticket with results
RT Query Syntax Examples
Status = 'new'
Status = 'open' AND Owner = 'scott'
Subject LIKE 'checklist'
Queue = 'Professional'
Created > '2025-01-01'
Owner = 'Nobody'
Security
This server is built with security in mind:
- SecretStr: Passwords are stored using Pydantic's SecretStr to prevent accidental logging
- Error Sanitization: Credentials are scrubbed from all error messages
- No Filesystem Access: The server never reads or writes files
- No Shell Execution: No subprocess or shell commands
- Minimal Dependencies: Only essential packages to reduce attack surface
- Automated CVE Scanning: Weekly security scans via GitHub Actions
- Container Security: Built on Hummingbird images with minimal CVE count
See SECURITY.md for the full security design document.
Development
# Clone the repository
git clone https://github.com/crunchtools/mcp-request-tracker.git
cd mcp-request-tracker
# Install dependencies
uv sync --all-extras
# Run tests
uv run pytest
# Lint
uv run ruff check src tests
# Type check
uv run mypy src
License
This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). See LICENSE for details.
Request Tracker MCP questions
How do I add Request Tracker MCP to Claude Code?
Run claude mcp add mcp-request-tracker -- uvx mcp-request-tracker-crunchtools in your terminal. Add --scope user to make it available in every project.
How do I add Request Tracker MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Request Tracker MCP provide?
It exposes 16 tools, including search_tickets, get_ticket, get_ticket_history, get_my_open_tickets, get_new_tickets.
How can I search for tickets?
You can search for tickets using RT query syntax, such as filtering by status, owner, subject, or queue.
Does this server support time tracking?
Yes, you can set total time worked or add time to existing entries on a ticket.
Is my password safe when using this server?
Yes, passwords are stored as SecretStr to prevent logging and credentials are scrubbed from error messages.
Can I add comments to tickets?
Yes, you can add private comments that are not visible to the requestor or correspondence that is visible to them.