JSON-RPC server foundation
The MCP server supports initialize, tools/list, tools/call, resources/list and resources/read over stdio JSON-RPC framing.
MCP Integration.
MCP tool boundaries for automation that uses Limvero public API rules instead of bypassing them.
Implemented MCP boundary
MCP is intentionally narrow and uses the same tenant-scoped public API path as other integrations.
Menu list tool
limvero_list_menu_items routes through the same Public API and requires a tenant API key with the required read scopes.
Order list tool
limvero_list_orders routes through the same Public API and uses bounded arguments before API calls.
Input validation
MCP tool arguments are allowlisted and bounded before Public API calls, so tools cannot bypass endpoint validation.
Tenant and scope boundary
MCP uses LIMVERO_API_KEY and cannot bypass tenant scope, API key scopes, backend business rules or public endpoint limits.
No write automation by default
Write-heavy automation remains provider/customer-specific until public write endpoints and approval workflows are implemented.
Automation should start with read-only menu and order list workflows, then expand only after public API and approval controls are implemented for additional actions.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.