Ticket Fighter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPTCHA_API_KEY | No | 2Captcha API key — auto-solves reCAPTCHA v2 (NYC) and hCaptcha (Chicago) | |
| GOOGLE_CLIENT_ID | No | Google OAuth client ID — enables Gmail API for decision tracking | |
| GOOGLE_REDIRECT_URI | No | OAuth callback URL (e.g. https://tf.mmp.chat/auth/gmail/callback) | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manage_platesC | Add, remove, or list saved license plates for ticket monitoring |
| check_ticketsA | Check for open parking tickets by scraping city violation portals. Checks all saved plates if no plate specified. |
| analyze_ticketA | Gather evidence for a specific violation: ticket details, registration cross-ref, Street View imagery, traffic rule lookup, common defenses, and past dispute history |
| generate_disputeA | Format dispute arguments into city-specific form structure. Returns a preview — does NOT submit. |
| submit_disputeB | Submit a previously previewed dispute. Requires confirmed=true as a safety gate. |
| check_statusB | Check dispute status via city portal scrape or Gmail search for decision emails |
| setup_gmailA | Launch a visible browser for Gmail login. Saves auth state for headless reuse by check_status. |
| open_dashboardB | Open the Ticket Fighter dashboard in the MCP App UI. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Ticket Fighter | Ticket Fighter — parking ticket dashboard and dispute assistant |
TDQS
Scored across 8 tools
Each tool targets a distinct step or resource in the parking ticket dispute workflow. check_tickets (open tickets) and check_status (dispute status) are clearly differentiated by their descriptions, and generate_dispute vs submit_dispute is explicitly separated by preview vs actual submission.
All tool names follow a consistent verb_noun snake_case pattern: manage_plates, check_tickets, analyze_ticket, generate_dispute, check_status, submit_dispute, setup_gmail, open_dashboard. The convention is predictable and easy to parse.
Eight tools is well-scoped for a parking ticket dispute assistant. Each tool maps to a clear step or utility, with no redundant or filler tools.
The set covers the full lifecycle: plate management, ticket checking, evidence analysis, dispute generation, submission, status checking, Gmail setup, and dashboard access. Minor gaps exist, such as no explicit tool to update, cancel, or list all disputes, but core workflows are fully supported.