Progresso MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Progresso MCP list my open tickets"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Progresso MCP
Hand the live Progresso workspace (same Supabase as progresso.rritjesade.com) to any MCP client — Cursor, Claude Desktop, Inspector, etc.
Docs: https://progresso.rritjesade.com/docs/mcp · Admins: Settings → Connectors
One-command (Cursor)
{
"mcpServers": {
"progresso": {
"command": "npx",
"args": ["-y", "github:cetijunior/progresso-mcp"],
"env": {
"SUPABASE_URL": "https://dtigibuhzhmxrkfzvijt.supabase.co",
"SUPABASE_ANON_KEY": "sb_publishable_…",
"PROGRESSO_REFRESH_TOKEN": "…"
}
}
}
}Copy your refresh token from Settings → Connectors (web or Mac). Prefer refresh over access JWT. Never use the service-role key.
When published to npm: npx -y progresso-mcp (same env).
Related MCP server: Supabase MCP Server
Local / Inspector
cp .env.example .env # URL, anon key, PROGRESSO_REFRESH_TOKEN
npm install
npm run build
npm run inspectorTools (v0.2)
Tool | Purpose |
| Financials + presence + WIP count |
| Board work |
| CRM |
| Projects |
| Time |
Available Tools
15 toolsadd_commentC
Add a comment on a ticket (supports @Name mentions in body text).
Inputs: body (required), ticket_id (required).
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).
Inputs: ticket_id.
check_outA
Check out for today. Running timers are stopped with an auto note.
Inputs: no named parameters.
create_leadC
Create a CRM lead.
Inputs: name (required), notes, status, company, +2 more.
create_ticketA
Create a ticket (or sub-ticket via parent_id). Prefer zz-scratch boards when testing live.
Inputs: title (required), status, board_id, parent_id, +1 more.
dashboard_pulseC
Agency pulse: financials summary, who's checked in, in-progress ticket count.
Inputs: no named parameters.
get_ticketB
Fetch one ticket plus its sub-tickets.
Inputs: ticket_id (required).
list_leadsB
List CRM leads (newest first).
Inputs: limit, status.
list_projectsC
List projects with status.
Inputs: status.
list_ticketsB
List top-level tickets, optionally filtered by board_id or status.
Inputs: limit, status, board_id.
move_ticketC
Move a ticket to a new column (status) and optional position.
Inputs: status (required), ticket_id (required), position.
stop_timerC
Stop the running timer. Work note is required.
Inputs: note (required).
update_leadC
Patch a lead's status, temperature, or follow-up date (YYYY-MM-DD).
Inputs: lead_id (required), status, temperature, next_follow_up.
update_projectC
Patch a project's name, description, or status.
Inputs: project_id (required), name, status, description.
update_ticketC
Patch ticket fields (title, description, status, due_at, payment).
Inputs: ticket_id (required), title, amount, due_at, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
MCP server for interacting with the Supabase platform
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
Issues, projects, cycles, and roadmaps via the official Linear hosted MCP server.
Manage Timequip projects, tasks, comments, members, and dashboards through MCP.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for Supabase database and storage operations, enabling querying, inserting, updating, deleting rows, schema introspection, and file storage management.1216 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes your application's resources and tools as an MCP server using Supabase Auth, Postgres, and Row Level Security, allowing authorized users to connect via compatible MCP clients.339 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables CRUD management of tasks, workspaces, and notes via a remote MCP server with Supabase authentication and synchronization across Linux, Android, and ChatGPT.MIT
- FlicenseNot gradedqualityCmaintenanceEnables turning an existing Supabase database and Edge Functions into an MCP server, exposing selected tables with Row Level Security and Edge Functions as tools for use in MCP clients.-