Skip to main content
Glama

Related Servers

Alternatives to smaregi-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables Claude and other MCP clients to read and write a Loyverse point-of-sale account, covering catalogue items, inventory levels, loyalty customers, receipts and refunds through natural language. Includes a one-call sales summary that aggregates any date range into totals and ranked breakdowns by day, item, category, payment type, employee or store.
      41
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes a curated subset of the Officegest API v2 (22 CRUD tools) for managing clients, sales, and stock to AI clients like Claude Code and Claude Desktop.
      1
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with a point-of-sale public API through 32 MCP tools for managing bills, customers, items, orders, receipts, stock, suppliers, taxes, and webhooks over stdio and HTTP transports.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query a retail and food-service point-of-sale database through predefined business tools for sales summaries, top products, margins, stagnant inventory, cash reconciliation, and optional stock adjustments, returning formatted markdown answers.
      -
    • F
      license
      C
      quality
      A
      maintenance
      Enables Claude or any MCP client to query a Toast POS using plain English, with 55 read-only tools covering orders, sales, labor, employees, menus, inventory, customers, and cash.
      55
      -

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct purpose: HTTP methods (GET, POST, PUT, PATCH, DELETE) are clearly separated, and auxiliary tools (list_paths, auth_status, configure, server_info) handle specific non-API operations with no overlap.

    Naming Consistency5/5

    All tools use a consistent snake_case pattern with the 'smaregi_' prefix. HTTP method tools follow 'smaregi_api_<method>' and other tools use descriptive names like 'smaregi_auth_status', maintaining a predictable structure.

    Tool Count5/5

    With 9 tools, the server covers essential API operations (all common HTTP methods) and administrative functions (auth, configuration, info). This count is well-scoped for a general-purpose API wrapper without being bloated or sparse.

    Completeness5/5

    The tool set fully covers the lifecycle of interacting with a REST API: all CRUD methods (GET, POST, PUT, PATCH, DELETE) are present, plus endpoint discovery (list_paths), authentication status, configuration, and server info. No obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues