Skip to main content
Glama
UserVanya

iikocloud-mcp

by UserVanya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to iikocloud-mcp

No user-submitted related servers found.

    Related Servers

    • iikoServer MCP Server

      simba87
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for iiko restaurant management system REST API, providing 39 tools to manage products, employees, entities, documents, payments, reports, and raw API access.
      1
      -

    • mcp-server

      gwanghun-choi
      A
      license
      Not graded
      quality
      C
      maintenance
      A universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.
      Academic Free v1.1

    • OpenAPI MCP Server

      luciVuc
      A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.
      18 npm
      MIT

    • AccelMCP

      t-ogawa-dev
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.
      -
    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

    B3/5.0

    Scored across 106 tools

    Disambiguation2/5

    Many tools are duplicated with two arg styles (e.g., dictionaries__get_cancel_causes vs dictionaries__get_cancel_causes_by_organization), making it hard to pick the right one. Customer lookup tools also overlap heavily, and deliveries_retrieve has several similar retrieval variants. Descriptions are detailed, but boundaries between many tools remain unclear.

    Naming Consistency4/5

    Tools follow a consistent category__verb_noun snake_case pattern throughout (e.g., customers__get_customer_by_id, invoice_processing__list_inventory_writeoff_documents). Minor inconsistencies exist such as get_delivery_by_id vs get_deliveries_by_id and mixed singular/plural forms, but the overall convention is predictable and readable.

    Tool Count1/5

    106 tools is far beyond a manageable MCP surface, and many are thin wrappers or duplicate variants of the same operation. Even for a broad iikoCloud API, this is an extreme count that will overwhelm an agent and increase misselection.

    Completeness2/5

    The toolset is overwhelmingly read-only: there are no create/update/delete tools for customers, orders, deliveries, menu, or webhooks, despite including operations__wait_command that references write-tools. Gaps like send_sms (only checks) and no mutation endpoints mean agents cannot complete lifecycle workflows. The read side is broad, but the surface is incomplete for real operations.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources