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

AI-generated 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.
Before you install
The assistant can change real ticket data: ownership, status, resolution, comments, replies and time entries are written to your RT instance. It needs your RT password (RT_PASS) and possibly HTTP Basic Auth credentials, so store them in the MCP client configuration rather than in shared files. Replies are visible to requestors.

Installation

In SourceWeft

  1. Open MCP Request-tracker in the dashboard and add it to a workspace.
  2. 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)

bash
uvx mcp-request-tracker-crunchtools

Option 2: Using pip

bash
pip install mcp-request-tracker-crunchtools

Option 3: Using Container

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

Configuration

Set the following environment variables:

VariableRequiredDescription
RT_URLYesBase URL of your RT server
RT_USERYesRT username
RT_PASSYesRT password
RT_HTTP_USERNoHTTP Basic Auth username
RT_HTTP_PASSNoHTTP Basic Auth password

Usage with Claude Code

Using uvx

bash
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

bash
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 syntax
  • get_ticket - Get ticket details
  • get_ticket_history - Get ticket history/changelog
  • get_my_open_tickets - Get open tickets for a user
  • get_new_tickets - Get new/unassigned tickets

Update Tickets

  • set_ticket_owner - Set ticket owner
  • set_ticket_status - Set ticket status
  • open_ticket - Open a ticket
  • resolve_ticket - Resolve/close a ticket
  • take_ticket - Take ownership and open

Time Tracking

  • set_time_worked - Set total time worked
  • add_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

bash
# Clone the repositorygit clone https://github.com/crunchtools/mcp-request-tracker.gitcd mcp-request-tracker
# Install dependenciesuv sync --all-extras
# Run testsuv run pytest
# Lintuv run ruff check src tests
# Type checkuv run mypy src

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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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