Payhip MCP Server
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. Required for the local stdio server and for Authorization headers; 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.
Payhip through Cotlet.dev. Call payhip_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 |
|---|---|
| payhip_guideA | How to work in Payhip (orders, products and sales reports): its screens and the sign-in link. Call this first. |
| payhip_statusA | Check that your Cotlet.dev account and Payhip are ready: account, credits and Payhip connection. |
| payhip_openA | Open a Payhip page in your signed-in Cloud Browser (default https://payhip.com) to work with orders, products and sales reports. |
| payhip_readA | Read the current Payhip page: its text and numbered buttons, links and fields. |
| payhip_clickB | Click a numbered element on the current Payhip page. |
| payhip_typeB | Type text into a numbered field on the current Payhip page. |
| payhip_closeA | Close the Payhip 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 has a clearly distinct role: guidance, readiness check, browser lifecycle, page reading, clicking, typing, and closing. The only mild overlap is between the guide and status tools, but their descriptions make the boundary clear.
All tools use the consistent payhip_ prefix and snake_case, which is predictable. However, guide and status are noun-like names while the others are verbs, a minor deviation from a pure verb_noun pattern.
Seven tools is well-scoped for a browser automation server targeting Payhip. Each tool corresponds to a necessary phase of the workflow without redundant operations.
The core browser automation lifecycle is covered: onboarding, opening, reading, clicking, typing, and closing. Minor gaps exist around explicit navigation, scrolling, or selecting dropdowns, but most Payhip workflows can be handled with the provided tools.