MCP Request Tracker CrunchTools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RT_URL | Yes | Base URL of your RT server | |
| RT_PASS | Yes | RT password | |
| RT_USER | Yes | RT username | |
| RT_HTTP_PASS | No | HTTP Basic Auth password | |
| RT_HTTP_USER | No | HTTP Basic Auth username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tickets_toolB | Search for tickets using RT query syntax. |
| get_ticket_toolB | Get details of a specific ticket. |
| get_ticket_history_toolB | Get the history/changelog of a ticket. |
| get_my_open_tickets_toolA | Get all open tickets assigned to a user. |
| get_new_tickets_toolA | Get all new (unassigned) tickets, optionally filtered by queue. |
| set_ticket_owner_toolB | Set the owner of a ticket (take/assign ticket). |
| set_ticket_status_toolC | Set the status of a ticket. |
| update_ticket_toolB | Update ticket fields (subject, priority, queue). All fields are optional. |
| resolve_ticket_toolC | Resolve/close a ticket, optionally adding a comment. |
| open_ticket_toolA | Open a ticket (change status from new to open), optionally taking ownership. |
| take_ticket_toolC | Take ownership of a ticket and open it. |
| set_time_worked_toolB | Set the total time worked on a ticket. |
| add_time_worked_toolB | Add time to the time worked on a ticket. |
| add_ticket_comment_toolA | Add a private comment/note to a ticket (not visible to requestor). |
| reply_to_ticket_toolA | Reply to a ticket (correspondence visible to requestor). |
| create_ticket_toolC | Create a new ticket. |
| complete_weekly_checklist_toolA | Complete a weekly checklist ticket with results. This is a workflow shortcut that:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/crunchtools/mcp-request-tracker'
If you have feedback or need assistance with the MCP directory API, please join our Discord server