MCP Request MCP Server

If you already use MCP Request, the mcp request mcp server is the piece that lets your assistant work with it directly. Secure MCP server for Request Tracker (RT) ticket management.

What the server does

• 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

mcp-request-tracker-crunchtools on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Communication — The Communication tool exposed by this server
• Creation — The Creation tool exposed by this server
• Workflows — The Workflows tool exposed by this server

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Request's toolset — Communication, Creation, Workflows — is a fair guide to whether it matches your workflow. It is maintained by crunchtools; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.