Skiddle MCP Server
# Skiddle MCP server for ChatGPT and Claude
Connect ChatGPT, Claude and other AI agents to Skiddle through Cotlet.dev. The live integration page documents 15 hosted operations for promoter events, tickets, orders, sales, guestlists and discount codes. The connection uses your signed-in Promotion Centre account.
## What you can ask
> Check ticket sales for my upcoming events.
> Find an order for a customer in this event.
> Prepare guestlist tickets for my approval.
> Prepare a single-ticket refund for my approval.
> Close a ticket type and reopen it later.
## Connect Skiddle
Start at https://cotlet.dev/signup?app=skiddle, sign in to Skiddle in its Cloud Browser and enable it for agents. For editors and scripts, create your API key in the Cotlet.dev console and export it as `COTLET_API_KEY`.
### ChatGPT
Add `https://cotlet.dev/mcp/v1/connect` as a connector and sign in with Cotlet.dev.
### Claude
Add `https://cotlet.dev/mcp/v1/connect` in Settings > Connectors and sign in with Cotlet.dev.
### Claude Code
```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```
### Cursor
Copy `.cursor/mcp.json` from this repo into your project:
```json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}
```
## Local browser adapter (stdio)
This repo contains a local MCP adapter for the hosted Cotlet.dev Cloud Browser. The seven local browser helpers below are distinct from the 15 Skiddle operations documented on the integration page. It speaks MCP over stdio, lists its Skiddle tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.
Run the adapter directly from this repository:
```bash
export COTLET_API_KEY="your-key"
python3 skiddle_agent.py serve
```
Or with Docker:
```bash
docker build -t skiddle-mcp .
docker run -i --rm -e COTLET_API_KEY skiddle-mcp
```
Tools: `skiddle_guide`, `skiddle_status`, `skiddle_open`, `skiddle_read`, `skiddle_click`, `skiddle_type`, `skiddle_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".
## Command line
Python 3.10+, using the standard library. From this repository:
```bash
export COTLET_API_KEY="your-key"
python3 skiddle_agent.py connect # ready config for Claude Code, Cursor, ChatGPT
python3 skiddle_agent.py status # is Skiddle ready in your Cotlet.dev account
python3 skiddle_agent.py guide # Skiddle screens and sign-in link
python3 skiddle_agent.py read # open Skiddle, read the page, close the browser
python3 skiddle_agent.py tools # list Cotlet.dev tools
python3 skiddle_agent.py serve # start the stdio MCP server (same as no argument)
```
## Questions from Skiddle users
**Which Skiddle login does this use?**
Use the new Promotion Centre at app.promotioncentre.co.uk. Listings + Tickets permissions cover events and tickets; Customer Data is needed for order details.
**Which actions ask for approval?**
Guestlist tickets, refunds and resending an order receipt ask for approval by default. These actions email a person or move money.
**Can the agent cancel an event?**
No. Cancelling or postponing a whole event is handled in Skiddle. The refund operation handles individual orders or tickets.
**Is this an official Skiddle integration?**
No. Cotlet.dev is independent and is not affiliated with Skiddle Ltd.
## Source
https://cotlet.dev/integrations/skiddle-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=skiddle
Start here: https://cotlet.dev/signup?app=skiddle
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.