Skip to main content
Glama
AutoRepair Cloud MCP server

AutoRepair Cloud MCP server

Related Servers

Alternatives to AutoRepair Cloud MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects MCP clients to an AI browser so agents can open and read pages, click, type, fill forms, take screenshots, and search within the user's logged-in browser session. Sensitive actions such as checkouts or payments require explicit approval.
      MIT
    • 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
      Connects an AI assistant to a dealer account so it can build and link a shop website that shows live vehicle stock and takes enquiries and test-drive bookings with no database to run. It also lets the assistant read and change listings, prices, test drives, reviews and leads in plain language, with read-only access by default and every change written to an audit log.
      35 npm
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents like ChatGPT and Claude to work inside a signed-in Stayflexi hotel account through a hosted cloud browser, handling outlet sales review, table orders, folio charges, and outlet setup with user confirmation before changes are made.
      Elastic 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Connects a signed-in Phorest account to AI agents, enabling natural-language appointment booking and rebooking, schedule and gap checks, client history queries, and client-card notes without a Phorest API key.
      7
      Elastic 2.0

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: guide, status, open, read, click, type, and close map to separate phases or browser actions. There is no meaningful overlap between reading, clicking, typing, opening, and closing.

    Naming Consistency5/5

    All tools consistently use the autorepair_cloud_ prefix followed by a short action-oriented name. The snake_case pattern is predictable throughout.

    Tool Count5/5

    Seven tools is well-scoped for a browser-based workflow server. Each tool covers an essential step: orientation, readiness, session lifecycle, and page interaction.

    Completeness4/5

    The surface covers the core browser workflow: open, read, click, type, close, plus guidance and status checks. Minor gaps exist around explicit navigation, waiting, scrolling, and select/dropdown handling, but most tasks can likely be worked around with read/click/type.