Back to all documentation

Connect Progresso with MCP

Give an MCP-compatible assistant access to your live Progresso workspace, with the same permissions as your signed-in account.

Quick setup

  1. 1

    Open connector settings

    Sign in to Progresso, open Settings → MCP connector, then choose “Copy MCP config”.

  2. 2

    Paste the configuration into your MCP client

    Add it to your client’s MCP server configuration and save the file.

  3. 3

    Restart the client and test the connection

    Ask it to run dashboard_pulse or list your Progresso tickets.

Open connector settings

Configuration format

The settings screen fills these values automatically. This example is only a reference.

{
  "mcpServers": {
    "progresso": {
      "command": "npx",
      "args": ["-y", "github:cetijunior/progresso-mcp"],
      "env": {
        "SUPABASE_URL": "https://YOUR-PROJECT.supabase.co",
        "SUPABASE_ANON_KEY": "YOUR_PUBLIC_ANON_KEY",
        "PROGRESSO_REFRESH_TOKEN": "YOUR_REFRESH_TOKEN"
      }
    }
  }
}

Refresh token

Recommended. It lets the MCP server renew short-lived access automatically. If authentication later fails, refresh the credentials in Progresso and replace the token in your client.

Access token

Useful for a temporary test, but it expires quickly. Set it as PROGRESSO_ACCESS_TOKEN instead of the refresh token.

Security

  • Never use or expose the Supabase service-role key.
  • Never commit tokens or MCP configuration containing tokens to Git.
  • The MCP server follows your Progresso role and database access rules.
  • Sign out globally if you believe a token has been exposed, then sign in again.

Available tools

dashboard_pulse

Agency summary, presence, and work in progress

list_tickets / get_ticket

Read ticket and board work

create_ticket / update_ticket

Create, edit, and move work

list_leads / update_lead

Work with the CRM pipeline

list_projects / update_project

Read and update projects

check_in / check_out / stop_timer

Manage time tracking