Skip to main content
Glama
Procured MCP Server

Procured MCP Server

Related Servers

Alternatives to Procured MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT, Claude, and other AI agents to draft estimates, schedule jobs, assign crew members, and review receivables in a user's signed-in business account, requiring approval before actions reach other people.
      7
      Elastic 2.0
    • A
      license
      A
      quality
      Not graded
      maintenance
      Connects ChatGPT, Claude, and other AI agents to a user's Billdr account through hosted workflow tools for projects, budgets, quotes, change orders, invoices, timesheets, and client reports. Write actions require approval by default.
      7
      Elastic 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects a signed-in Trusso account to ChatGPT, Claude, and other AI agents so users can read jobs and crews, draft estimates, schedule work, and manage invoices, with write actions requiring approval by default.
      Elastic 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with 220+ tools for building websites, sending email, managing contacts, invoicing, databases, automation, and more through a single secure connection. Features hardware-bound authentication and works with Claude Desktop, Claude Code, Cursor, and other MCP-compatible clients.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects a signed-in InvoiceASAP account to ChatGPT, Claude and other AI agents so they can review unpaid invoices, customer balances and aging, sales reports by item or representative, and job photos. Actions that change data, such as marking an invoice paid or altering payment settings, wait for the user's approval.
      Elastic 2.0

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: guide, readiness check, open session, read page, click, type, and close. The browser interaction tools are separated by action, and the setup tools target different concerns.

    Naming Consistency4/5

    All tools use a consistent procured_ prefix and snake_case single-word names. The only minor inconsistency is that guide and status are noun-like while the others are verbs, but the pattern remains predictable.

    Tool Count5/5

    Seven tools is well scoped for a browser-session wrapper around a web app. Each tool covers a necessary part of the lifecycle: setup, opening, reading, interacting, and closing.

    Completeness4/5

    The surface covers the core browser automation lifecycle and readiness checks. Minor gaps exist around advanced page interaction such as scrolling, waits, or selecting dropdown options, but agents can likely work around them via read/click/type.