Skip to main content
Glama
Novigante

mcp-loyverse

by Novigante
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-loyverse

No user-submitted related servers found.

    Related Servers

    • clover-mcp

      SBolivarLoL
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the Clover POS REST API that gives AI assistants read and safe-write access to a merchant's sales, inventory, orders, and customers.
      56
      MIT

    • mcploy

      ogarciabrena
      A
      license
      A
      quality
      D
      maintenance
      Exposes the Loyverse API as MCP tools to manage stores, products, inventory, customers, receipts, and more from AI assistants.
      54
      MIT

    • spendglass

      shawn-durrani
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server that lets local AI agents query bank transactions stored in a local SQLite database, with tools for accounts, transaction search, spending summaries, recurring charges, trends, themes, subscriptions, and store health.
      2
      MIT

    • toconline-mcp

      themiguelamador
      A
      license
      B
      quality
      C
      maintenance
      Local MCP server for TOCOnline accounting/invoicing API that enables AI assistants to manage customers, products, sales documents, and call arbitrary endpoints via natural language after OAuth login.
      67
      1
      MIT

    • ripio-community-mcp

      ruizemanuel
      A
      license
      A
      quality
      A
      maintenance
      A local, read-only MCP server that lets AI assistants securely access your Ripio account to retrieve balances, activity, prices, limits, and open orders using your own API key.
      10
      144 npm
      MIT

    • FreeAgent MCP

      duncanmcclean
      F
      license
      Not graded
      quality
      B
      maintenance
      A local, read-only MCP server that exposes FreeAgent accounting data to AI clients, enabling natural language queries about balances, transactions, categories, and financial reports.
      2
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each core entity (employees, receipts, items, customers, stores) has a clearly distinct list vs. get pair. Analytics tools such as sales_summary, top_selling_items, and top_employees_by_sales target different questions and do not overlap with the catalog or receipt lookup tools.

    Naming Consistency4/5

    The set predominantly follows a consistent snake_case verb_noun convention, e.g. list_employees, get_receipt, top_selling_items. The main deviation is healthcheck, which would be more consistent as health_check, but it is a minor and readable exception.

    Tool Count5/5

    With 15 tools, the server is comfortably scoped for a POS data and reporting integration. Each major entity gets list/get coverage, while analytics and healthcheck add clear value without bloating the surface.

    Completeness4/5

    The tool set covers list/get access for employees, receipts, items, customers, stores, and merchant profile, plus useful sales and ranking analytics. It lacks create/update/delete operations, but for a read-only reporting MCP server the surface is nearly complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources