Skip to main content
Glama
Restroworks Restaurant POS MCP server

Restroworks Restaurant POS MCP server

Related Servers

Alternatives to Restroworks Restaurant POS MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and safely configure point-of-sale accounts across multi-location restaurant and café networks, with dry-run-by-default writes, account allow-lists, and audit logging.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query live restaurant sales, orders, menus, opening hours, and operational health across locations and ordering channels. Access is read-only and scoped to what the signed-in user can see.
      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
      D
      maintenance
      Enables AI assistants to query live Toast POS data and generate sales, labor, and cash reports while answering restaurant operations questions, all in a read-only manner.
      33 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: guidance, readiness check, browser session open/close, page reading, clicking, and typing. The boundary between guide and status is explained well enough, and no two tools overlap in operation.

    Naming Consistency5/5

    All tools follow the same restroworks_restaurant_pos_<action> pattern with a consistent shared prefix. The action suffixes are simple and predictable.

    Tool Count5/5

    Seven tools is a well-scoped set for a browser-driven POS automation server. Each tool maps to an essential workflow primitive, with no obvious padding.

    Completeness4/5

    The set covers the core browser automation lifecycle: orient, check readiness, open, read, click, type, and close. Minor gaps exist around explicit navigation/back/refresh, waiting for page load, or keyboard actions, but agents can likely work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues