Progresso MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dashboard_pulseC | Agency pulse: financials summary, who's checked in, in-progress ticket count. |
| list_ticketsB | List top-level tickets, optionally filtered by board_id or status. |
| get_ticketB | Fetch one ticket plus its sub-tickets. |
| create_ticketA | Create a ticket (or sub-ticket via parent_id). Prefer zz-scratch boards when testing live. |
| update_ticketC | Patch ticket fields (title, description, status, due_at, payment). |
| move_ticketC | Move a ticket to a new column (status) and optional position. |
| add_commentC | Add a comment on a ticket (supports @Name mentions in body text). |
| list_leadsB | List CRM leads (newest first). |
| create_leadC | Create a CRM lead. |
| update_leadC | Patch a lead's status, temperature, or follow-up date (YYYY-MM-DD). |
| check_inA | Check in for today. Optionally start a timer on a ticket (omit ticket_id for presence-only if you are admin — still recommended to pass a ticket). |
| check_outA | Check out for today. Running timers are stopped with an auto note. |
| stop_timerC | Stop the running timer. Work note is required. |
| list_projectsC | List projects with status. |
| update_projectC | Patch a project's name, description, or status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes: ticket lifecycle (create/update/move/get/list), leads (list/create/update), project management (list/update), and time tracking (check_in/check_out/stop_timer). The main overlap is move_ticket vs update_ticket since moving is essentially updating status, though the descriptions clarify move is column-specific while update is general field patching. dashboard_pulse is distinct enough as an aggregate view.
Most tools follow a consistent verb_noun pattern (list_tickets, create_ticket, update_ticket, move_ticket, list_leads, create_lead, update_lead, list_projects, update_project). Minor deviations exist like check_in/check_out/stop_timer and dashboard_pulse which don't follow the resource-noun pattern, but they're still understandable and follow predictable verb-first phrasing.
15 tools for an agency management/progress tracking server is well-scoped. Each tool covers a distinct functional area: tickets, leads, projects, time tracking, and dashboard aggregate. The count feels complete without being bloated, and each tool appears necessary for the stated purpose.
Ticket management is thorough (list, get, create, update, move, comment), and leads/projects have basic CRUD. However, there are notable gaps: no way to delete tickets, leads, or projects; no tool to list tickets for a specific ticket's sub-tickets (only get_ticket for one); CRM has no way to view individual lead details separately from the list; and there's no tool to list or view project details beyond the list. The time-tracking tools depend on tickets but their interaction with the ticket surface feels slightly disconnected.