Skip to main content
Glama
Restroworks Restaurant POS MCP server

Restroworks Restaurant POS MCP server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key, available at https://cotlet.dev/app. Sent as the Authorization Bearer token (e.g. `Authorization: Bearer $COTLET_API_KEY`) or exported as the COTLET_API_KEY environment variable for the local stdio server. Without it, tool calls fail with: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Restroworks Restaurant POS through Cotlet.dev. Call restroworks_restaurant_pos_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
restroworks_restaurant_pos_guideA

How to work in Restroworks Restaurant POS (review outlet sales, orders, inventory and menus): its screens and the sign-in link. Call this first.

restroworks_restaurant_pos_statusB

Check that your Cotlet.dev account and Restroworks Restaurant POS are ready: account, credits and Restroworks Restaurant POS connection.

restroworks_restaurant_pos_openB

Open a Restroworks Restaurant POS page in your signed-in Cloud Browser (default https://restroworks.biz) to work with review outlet sales, orders, inventory and menus.

restroworks_restaurant_pos_readA

Read the current Restroworks Restaurant POS page: its text and numbered buttons, links and fields.

restroworks_restaurant_pos_clickB

Click a numbered element on the current Restroworks Restaurant POS page.

restroworks_restaurant_pos_typeB

Type text into a numbered field on the current Restroworks Restaurant POS page.

restroworks_restaurant_pos_closeA

Close the Restroworks Restaurant POS browser session when the work is done, so credits stop running.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct role: guidance, readiness check, browser session open/close, page reading, clicking, and typing. The boundary between guide and status is explained well enough, and no two tools overlap in operation.

Naming Consistency5/5

All tools follow the same restroworks_restaurant_pos_<action> pattern with a consistent shared prefix. The action suffixes are simple and predictable.

Tool Count5/5

Seven tools is a well-scoped set for a browser-driven POS automation server. Each tool maps to an essential workflow primitive, with no obvious padding.

Completeness4/5

The set covers the core browser automation lifecycle: orient, check readiness, open, read, click, type, and close. Minor gaps exist around explicit navigation/back/refresh, waiting for page load, or keyboard actions, but agents can likely work around them.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues