Joy MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, created in the Cotlet.dev console and exported as COTLET_API_KEY. Required by the local stdio adapter and used as a Bearer token for the hosted MCP endpoint. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Joy through Cotlet.dev. Call joy_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 |
|---|---|
| joy_guideA | How to work in Joy (wedding guests, RSVPs, schedules, registry gifts and messages): its screens and the sign-in link. Call this first. |
| joy_statusA | Check that your Cotlet.dev account and Joy are ready: account, credits and Joy connection. |
| joy_openB | Open a Joy page in your signed-in Cloud Browser (default https://withjoy.com) to work with wedding guests, RSVPs, schedules, registry gifts and messages. |
| joy_readA | Read the current Joy page: its text and numbered buttons, links and fields. |
| joy_clickB | Click a numbered element on the current Joy page. |
| joy_typeB | Type text into a numbered field on the current Joy page. |
| joy_closeA | Close the Joy 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
Each tool maps to a distinct step in a browser-automation workflow: orientation (guide/status), session control (open/close), and page interaction (read/click/type). There is no meaningful overlap between any pair, and the descriptions reinforce ordering (guide first, close last).
All seven tools use a uniform joy_ prefix with a single lowercase verb (guide, status, open, read, click, type, close). The pattern is predictable and immediately readable.
Seven tools is well-scoped for a browser-driven site automation set: two onboarding/context tools, two session tools, and three interaction primitives. Nothing feels redundant or padded.
The lifecycle is well covered: orient, verify readiness, open session, read page, act, and close. Minor gaps exist for common browser needs like scrolling, keyboard/enter submission, screenshots, or handling multiple tabs, which agents would have to work around with click/type alone.