Skip to main content
Glama

Related Servers

Alternatives to Extrabat 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
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to securely access Twake Space team spaces, members, feeds, unread counts, votes, sign-offs, and meetings, and to perform actions as the user only after explicit prior approval.
      248 npm
      AGPL 3.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

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct phase or primitive of a browser-automation workflow: status (account/credit check), guide (instructions), open (navigation), read (page inspection), click, type, and close. There is no meaningful overlap between read/click/type/close since they operate on different page interactions, and status vs guide is clearly separated by 'check readiness' vs 'how to work'.

    Naming Consistency5/5

    All seven tools use the same snake_case 'extrabat_<verb>' convention with a shared namespace prefix. No camelCase mixing or vague standalone verbs; the pattern is immediately predictable.

    Tool Count5/5

    Seven tools is exactly the right scope for a minimal browser-automation agent: one setup check, one guide, and the five core primitives needed to open, read, interact with, and close a session. Every tool earns its place with no filler.

    Completeness4/5

    The surface covers the full session lifecycle (status → guide → open → read → click/type → close), which matches the stated purpose. Minor gaps remain for richer page interaction—no dedicated select/option handling, scrolling, or explicit navigation/back beyond 'open'—but agents can work around these via click and re-open.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues