Skip to main content
Glama
cetijunior

Progresso MCP

by cetijunior
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Progresso MCP

No user-submitted related servers found.

    Related Servers

    • App MCP

      elvinbaghele
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      -

    • Supabase MCP Server

      elsheppo
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes 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.
      255 npm
      2
      MIT

    • TodoAI MCP Server

      gneed49
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables CRUD management of tasks, workspaces, and notes via a remote MCP server with Supabase authentication and synchronization across Linux, Android, and ChatGPT.
      MIT

    • Supabase MCP Server

      dedalus-labs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure interaction with Supabase databases via the PostgREST API, supporting full CRUD operations and stored procedure calls. It utilizes the Dedalus MCP framework to provide encrypted credential handling and just-in-time token exchange.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources