Skiddle MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, used as a Bearer token for the hosted MCP server or by the local stdio adapter. Create it in the Cotlet.dev console and export it as COTLET_API_KEY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Skiddle through Cotlet.dev. Call skiddle_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 |
|---|---|
| skiddle_guideA | How to work in Skiddle (manage promoter events, tickets, orders, guestlists and discount codes): its screens and the sign-in link. Call this first. |
| skiddle_statusA | Check that your Cotlet.dev account and Skiddle are ready: account, credits and Skiddle connection. |
| skiddle_openB | Open a Skiddle page in your signed-in Cloud Browser (default https://app.promotioncentre.co.uk) to work with manage promoter events, tickets, orders, guestlists and discount codes. |
| skiddle_readA | Read the current Skiddle page: its text and numbered buttons, links and fields. |
| skiddle_clickC | Click a numbered element on the current Skiddle page. |
| skiddle_typeB | Type text into a numbered field on the current Skiddle page. |
| skiddle_closeA | Close the Skiddle 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: guide, status, open, read, click, type, and close map to separate parts of the workflow. There is little risk of confusing page-reading with clicking or typing, and the session lifecycle tools are distinct from interaction tools.
All tools use a consistent skiddle_ prefix and snake_case, which makes the set predictable. Most suffixes are clear verbs, though guide and status are noun-like labels rather than actions, a minor deviation.
Seven tools is well-scoped for a browser-automation workflow. Each tool earns its place across setup, guidance, page interaction, and session cleanup, with no obvious redundancy.
The set covers the core lifecycle: check readiness, open a session, read the page, click/type, and close to stop credits. Minor gaps like explicit scrolling, waiting, or keyboard shortcuts exist, but agents can likely work around them using the available read/click/type actions.