
MCP Request-tracker
io.github.crunchtoolsPublished by GitHub account crunchtoolsv0.1.1Updated Oct 27, 2026
Secure MCP server for Request Tracker (RT) ticket management
Overview
Local MCP server that lets an assistant search, read, create and update tickets in a Request Tracker (RT) helpdesk instance.
- What you can do
- Search and read tickets: query with RT syntax, view details, history, your open tickets and new unassigned ones
- Change ticket state: set owner or status, open, take, or resolve a ticket
- Log time: set total time worked or add time to a ticket
- Communicate: add a private comment or send a reply visible to the requestor
- Create tickets and run a pre-built weekly checklist workflow
- When to use it
- Useful when your team runs its support or request queue in Request Tracker and you want an assistant to triage, update, comment on and close tickets without switching to the RT web interface.
- Requirements
- Runs locally as a Python package (uvx or pip) or as a container. Requires a reachable RT server URL plus RT credentials in the environment variables RT_URL, RT_USER and RT_PASS; optional HTTP Basic Auth via RT_HTTP_USER and RT_HTTP_PASS. Desktop only.
Installation
In SourceWeft
- Open MCP Request-tracker in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP 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)
Option 2: Using pip
Option 3: Using Container
Configuration
Set the following environment variables:
Usage with Claude Code
Using uvx
Using Container
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
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
License
This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). See LICENSE for details.
Source: README.md at commit f115dc8
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts