MCP recipe server

pintours gp

Order attraction tickets on GreatPerks (Pintours) from any MCP client. There is no official API — so each tool hands your client a browser-harness recipe it runs locally against your own signed-in Chrome.

tools
3
stateless transport
HTTP
preview by default
$0
get a key
01

Connect

Add it as an HTTP connector. The endpoint is gated by your API key — create one at /keys. Claude Desktop can't send headers, so the key rides in the URL path; for Claude Code use the x-api-key header.

endpointhttps://pintours-gp.42nights.dev/api/mcp
claude desktop — connector url
https://pintours-gp.42nights.dev/api/mcp/<YOUR_KEY>
claude code cli
claude mcp add --transport http \
  --header "x-api-key: $PINTOURS_MCP_KEY" \
  pintours-gp https://pintours-gp.42nights.dev/api/mcp
02

Tools

3 greatperks_* tools. Each returns a Python recipe + payload schema. Ordering previews by default and stops at the PAY button — it only charges when you pass confirmOrder: true.

Catalog

greatperks_search_attractions

Search or list the whole catalog (~22.9k attractions) — each with its product URL. Read-only.

greatperks_get_attraction

Inspect one attraction: its ticket options, and per-option ticket types + bookable, priced dates.

Ordering

greatperks_place_order

Preview an order by default ($0, stops at the PAY button); charges only on explicit confirmOrder. Card stays in the gateway's iframe — automation never touches it.

03

What you need

  • browser-harness on your $PATH (the client runs the recipe; the server never touches a browser).
  • An isolated Chrome in a pintours.greatperks.com member session (the catalog loads, not the membership wall).
  • An MCP client with shell + file-write tools to run the recipe.