Progresso MCP
# Progresso MCP
Hand the **live** Progresso workspace (same Supabase as [progresso.rritjesade.com](https://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)
```json
{
"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).
## Local / Inspector
```bash
cp .env.example .env # URL, anon key, PROGRESSO_REFRESH_TOKEN
npm install
npm run build
npm run inspector
```
## Tools (v0.2)
| Tool | Purpose |
|------|---------|
| `dashboard_pulse` | Financials + presence + WIP count |
| `list_tickets` / `get_ticket` / `create_ticket` / `update_ticket` / `move_ticket` / `add_comment` | Board work |
| `list_leads` / `create_lead` / `update_lead` | CRM |
| `list_projects` / `update_project` | Projects |
| `check_in` / `check_out` / `stop_timer` | Time |
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.