iiko-mcp
Related Servers
Alternatives to iiko-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for iiko restaurant management system REST API, providing 39 tools to manage products, employees, entities, documents, payments, reports, and raw API access.1-
- AlicenseAqualityDmaintenanceA standalone MCP server for API debugging, login authentication, API configuration management, and indexed API execution.56 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes 236 iikoCloud API methods across 22 domains as configurable tools, supporting multi-tenancy with credentials passed through transport channels (HTTP headers or environment variables) for security.1-
- AlicenseAqualityCmaintenanceMCP server that provides tools for exploring and testing APIs through Swagger/OpenAPI documentation.5243 npm12MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for making API calls with authentication support. Allows configuring multiple API endpoints and performing GET, POST, PUT, DELETE requests, including form data and file uploads.-
- AlicenseAqualityAmaintenanceAn MCP server that helps you build against the Partner Center REST API, providing scenario discovery, REST examples, authentication guidance, and error decoding without making live API calls.2953 npm2MIT
TDQS
Scored across 6 tools
The tools are mostly distinct resources, but the universal iiko_request overlaps with every specific wrapper, creating potential confusion about which to use. Although iiko_request is clearly for debugging, an agent might still misselect it for a routine operation.
All tool names follow a consistent snake_case convention with the iiko_ prefix, and they all use noun-like resource names. The naming pattern is uniform and predictable across the set.
Six tools is a well-scoped number for an API integration server, covering core resources with a generic fallback. It is within the ideal 3-15 range and each tool earns its place.
The specialized tools cover the primary endpoints (organizations, nomenclature, stop lists, deliveries), and the iiko_request tool provides a catch-all for any other API operation. This ensures no functional gaps or dead ends.