clubready-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet API key, obtained at https://cotlet.dev/app. Used to authorize tool calls to the ClubReady MCP server. Without it, tool calls respond: "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.
ClubReady through Cotlet.dev. Call clubready_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clubready_guideA | How to work in ClubReady (manage customer profiles, memberships and club operations): its screens and the sign-in link. Call this first. |
| clubready_statusB | Check that your Cotlet.dev account and ClubReady are ready: account, credits and ClubReady connection. |
| clubready_openB | Open a ClubReady page in your signed-in Cloud Browser (default https://app.clubready.com) to work with manage customer profiles, memberships and club operations. |
| clubready_readB | Read the current ClubReady page: its text and numbered buttons, links and fields. |
| clubready_clickB | Click a numbered element on the current ClubReady page. |
| clubready_typeB | Type text into a numbered field on the current ClubReady page. |
| clubready_closeA | Close the ClubReady browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The core interaction tools (open, read, click, type, close) map to clearly distinct browser actions with no overlap. The only mild ambiguity is between clubready_guide (how-to/onboarding) and clubready_status (account/connection readiness), but their descriptions draw a usable line between instructions and diagnostics.
Every tool uses the same clubready_ prefix with a single lowercase verb-style suffix (guide, status, open, read, click, type, close). The pattern is fully predictable and consistent throughout.
Seven tools is well-scoped for a browser-session wrapper: onboarding/status, session lifecycle, and the four core page-interaction primitives. Each tool earns its place with no filler.
The lifecycle (open → read → click/type → close) plus status/guide covers basic workflows, but common web-form needs are absent: no scrolling, key presses (e.g. Enter), dropdown/select handling, or back/navigate control beyond opening a page. Agents may hit dead ends on longer pages or complex membership forms.