DICE MCP Server

Events, ticket tiers, sales and guest lists for DICE promoters.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/dice'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

DICE API and MCP server: Let your AI agent run your DICE shows.

DICE has no official MCP server. Its Ticket Holders API is GraphQL for DICE partners, with a token made in MIO, and it only reads: events, ticket types, orders, holders, returns and transfers (checked 27 Oct 2026). Cotlet runs 15 DICE tools hosted, over MCP for agents and REST for scripts, and 8 of them write.

Events, ticket tiers, sales and guest lists for DICE promoters. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

What can you automate in DICE?

  • Draft an event from a booking brief
  • Add the next ticket release
  • Report weekly sales per ticket type
  • Export the door list
  • Track returns and transfers
  • Tell ticket holders about a change

Does DICE have an MCP server or an API?

  • The API docs list two queries, node and viewer, and no mutation. Drafts, ticket types, price tiers, event edits and MIO Connect messages stay in MIO.
  • Zapier and n8n have no DICE app (both pages return 404). The built-in links are Mailchimp for buyers and checkout on your site, Spotify and YouTube.
  • A free GitHub CLI with an MCP mode runs on your API token and reads only. Other "DICE MCP" results read public listings, not your MIO.
What you needTicket Holders APIGitHub MCP serverCotlet
Sales, orders, holders, returns, transfersYes, raw ordersYes, with analyticsYes, summed per ticket type
Create and submit an event draftNoNoYes, submit after your OK
Add ticket types and price tiersReads them onlyNoYes, after your OK
Message ticket holders with MIO ConnectNoNoYes, after your OK
Needs a partner API tokenYes, from MIOYes, from MIONo, your MIO sign-in

Checked 27 Oct 2026. Sources: DICE Ticket Holders API reference, MIO ticketing terms (US), DICE for partners, Make It On DICE: User Guidelines (MIO Connect), DICE Help: United States Terms of Use, DICE CLI and MCP in printing-press-library

How does Cotlet connect to DICE?

  1. Sign in to DICE. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your MIO password, and no price, message or submission goes out until you approve it.

Connect DICE to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Enable DICE for agents. Sign up, sign in to MIO in its Cloud Browser and press Enable for agents.
  2. Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in your agent's MCP server or connector settings.
  3. Confirm who you are. Chat apps send you through a Cotlet sign-in. Editors, n8n and scripts take an API key from the console.

DICE shares https://cotlet.dev/mcp/v1 with every other app on your Cotlet account. Turned DICE on after you connected? Refresh the connector and the DICE tools appear.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-dice \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-dice": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-dice]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: dice_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: dice_write

How to use the DICE REST API

Create your Cotlet API key

Create a Cotlet API key with access to DICE and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect DICE in Cotlet and enable it for agents. Account access: Your own DICE partner (MIO) account, with email and password.

Make your first DICE API request

REST:

curl "https://cotlet.dev/api/v1/dice/events?limit=5" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read events and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "dice",
  "tool": "list_events",
  "result": {
    "events": [
      {
        "event_id": "ev_48213",
        "name": "Club Night",
        "state": "approved",
        "start": "2026-11-14T22:00:00+00:00",
        "venue": "The Warehouse",
        "allocation": 350
      },
      {
        "event_id": "ev_48377",
        "name": "Rooftop Session",
        "state": "draft",
        "start": "2026-12-05T19:00:00+00:00",
        "venue": "Skyline Terrace",
        "allocation": 200
      }
    ],
    "next_cursor": null
  }
}

Lists the events of your MIO account, soonest first. Filter by state or start date to find tonight's show or everything still in draft.

Use the event_id from each item in the other tools. Pages hold up to 100 events; pass next_cursor back as cursor.

limit: 1 to 100. Default: 25.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

DICE workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestTickets sold and face value, split by ticket type and sales channel. Use get_sales_summary in your configured content report.
MakeHTTP > Make a requestTickets returned by fans, with date, reason and the original order. Use list_returns in your configured content report.
Python or Node.jsREST APIWho holds a ticket now: name, ticket type and whether it was claimed. Use list_ticket_holders in your configured content report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads DICE; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

DICE API endpoints and MCP tools

Events, drafts and review

A new event starts as a draft fans cannot see. DICE reviews every submitted event and may decline it.

  • List events (list_events, read): Your events in MIO with state, dates, venue and total allocation.
  • Get event (get_event, read): Full event: description, artists, venue, announce and on-sale dates, ticket types and price tiers.
  • Create event (create_event, write): New event as a draft in MIO. Fans see nothing until you submit it and DICE approves it.
  • Submit event (submit_event, write, asks first): Send a draft to DICE for review. Once approved it is announced and goes on sale on its dates.
  • Update event (update_event, write, asks first): Change the date, times, venue, line-up or description of an event fans may already hold tickets for.
  • Cancel event (cancel_event, write, asks first): Cancel an event in MIO. Fans are told and refunds follow your DICE agreement.

Ticket types and price tiers

Prices in cents of the event currency. A tier moves on when the earlier one sells out or at a set time, never both.

  • Add ticket type (add_ticket_type, write, asks first): Add a ticket type to an event, with price, allocation and optional door price.
  • Add price tier (add_price_tier, write, asks first): Add a release to a ticket type that moves on after an allocation sells out or at a set time.
  • Update ticket type (update_ticket_type, write, asks first): Change the name, price, allocation or door price of a ticket type, or archive it to stop sales.

Sales, orders and door lists

Every order carries one sales channel: internet, door, free or external (such as Fever). Lists page at 100 rows.

  • Get sales summary (get_sales_summary, read): Tickets sold and face value, split by ticket type and sales channel.
  • List orders (list_orders, read): Orders with time, quantity, sales channel, totals and promo code used.
  • List ticket holders (list_ticket_holders, read): Who holds a ticket now: name, ticket type and whether it was claimed.
  • List returns (list_returns, read): Tickets returned by fans, with date, reason and the original order.
  • List transfers (list_transfers, read): Tickets passed from one fan to another, with date and orders.

MIO Connect

Event information only: DICE forbids discounts, other events and surveys here.

  • Message attendees (message_attendees, write, asks first): Send an operational message to ticket holders with MIO Connect, e.g. door times or entry info.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/dice-api-mcp-server#tools

Who can see my DICE session, and how do I revoke it?

  • What we store. Your signed-in MIO profile, AES-256-GCM, in Finland. Not your password.
  • What your agent gets. The 15 DICE tools. No cookie, no API token.
  • What the session sees. What your MIO role sees: events, sales, ticket holders' names.
  • What no tool touches. Payouts, bank details, team members and account settings.
  • If MIO signs you out. You get an email with a sign-in link. We never sign in for you.
  • How to cut access. Disable for agents, reset the browser or delete the key. The next call stops.

DICE's MIO guidelines make you answer for anyone you give access to, so treat the Cloud Browser like a guest login you can end in one click. Our site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results); no SOC 2 report or third-party pentest yet.

Is it against DICE's terms? Account safety

use software, devices, or other manual or automated processes to "crawl" any page of our website, App or Services, including but not limited to any use of any scripts or web crawlers

DICE United States Terms of Use, 8.4, 10 Mar 2026

The MIO User Guidelines (17 Jun 2025) say they "supplement" those Terms of Use, and let DICE "revoke access to your DICE account" for any reason. The US self sign-up terms for promoters have no clause on bots or scripts. Cotlet clicks through MIO as you, which DICE could still call automation. We found no public case of a MIO account closed for it (checked 27 Oct 2026).

How we keep your account looking like you:

  • Your own MIO login, signed in by you
  • One Cloud Browser with its own IP and cookies
  • Prices, submissions, edits and fan messages wait for your OK
  • No ticket buying, no wait list tricks, no scraping of other promoters
  • If DICE objects, we pause the DICE tools for everyone within 24 h

MIO Connect is for event information only. A promo line in a door-time notice breaks DICE's guidelines, whoever sends it.

What happens when DICE changes?

  • 12 h between tests of the DICE reads and drafts
  • 24 h between tests of tiers and messages fans would see
  • $0 for a call to a DICE tool paused for repair

When MIO moves a field or renames a screen, the repair happens on our side. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Reads the tier on sale. Sold, left, and whether a later tier already waits.
  2. Measures the pace. Tickets in the last 7 days, days left at that rate.
  3. Waits for your OK. Price and size of the new release, in your Cotlet console.
  4. Reads it back. The full tier ladder after the change.
ActionUndo
Create a draftNothing to undo: fans never see a draft
Add a price tierChange or archive it; tickets already sold keep their price
Submit for reviewNo tool takes it back
Message ticket holdersNo, it cannot be unsent
Cancel an eventNo; refunds go to fans once you return the proceeds

7 of 15 tools ask first: every price, allocation, event edit, submission, message and cancellation. Only create_event runs at once, because a draft reaches nobody. Switch the wait off per tool for a scheduled run.

A new date is a reschedule under DICE's terms: fans may ask for refunds and you fund them. The agent stops and asks before it touches a date.

MCP call:

{
  "name": "add_price_tier",
  "arguments": {
    "ticket_type_id": "8841273",
    "name": "Second release",
    "price": 1800,
    "allocation": 150
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/dice/ticket-types/8841273/price-tiers \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Second release","price":1800,"allocation":150}'

Response:

{
  "ticket_type_id": "8841273",
  "price_tier_type": "allocation",
  "tiers": [
    {
      "id": "510922",
      "name": "Early bird",
      "price": 1500,
      "allocation": 100
    },
    {
      "id": "510987",
      "name": "Second release",
      "price": 1800,
      "allocation": 150
    }
  ]
}

The same tools answer over REST at /api/v1/dice, one key and one price, for cron jobs and BI scripts. A call your MIO role is not allowed to make fails and costs nothing. Each tool row above shows its REST path.

How much does the DICE MCP server cost?

About $16 a month for a promoter running 6 shows a month, 2,680 credits. DICE's own ticket fees do not change.

JobCallsCredits
Sales report with returns and transfers, weekly11 × 4440
Draft a show with two ticket types4 × 6240
Submit the draft for DICE review1 × 660
Add a second release4 × 3120
Door list on show day4 × 6240
Change notice to ticket holders4 × 280
Cloud Browser, 30 days1,500
Total2,680
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • No API token or partner contract needed

The month is our example: 6 shows, about 4 on sale at once, about 300 ticket holders each, so a door list is 3 pages. DICE publishes no figures for a typical promoter. Dollars at the $29 pack rate.

DICE MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
printing-press-library/dice-fmGo CLI and local MCP server on the Ticket Holders API: syncs events, orders, tickets, returns and transfers, then repeat buyers, tier performance and door lists. Hides fan names and emails from the model by default.Read only, by its own README. Needs a partner API token; runs on your computer. DICE folder last changed 11 Sep 2026.
pipeworx-io/mcp-diceHosted MCP with public event and venue listings from dice.fm.No buyer or holder data, about 20 to 30 events a browse. 0 stars.
Apify DICE scrapersPublic listings (line-ups, venues, prices), each also served through Apify's MCP.Public pages only, $0.50 to $4 per 1,000 results.
Ticket FairyAnother ticketing platform with a built-in assistant that changes events after approval.You move your shows and fans off DICE.

Reports only? The GitHub CLI on your own API token is free and fine. Fan-facing listings for a city guide come from the scrapers. If your agent should also draft shows, add releases and send door notices in MIO, that is what Cotlet does.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Behind Cotlet is Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the DICE tools go to contact@cotlet.dev.

DICE API and MCP: questions

How do I get access?

Open a free account at https://cotlet.dev, find DICE under Integrations in the console and sign in to MIO in its Cloud Browser. The trial starts when you sign up and asks for no card.

How do I connect DICE to ChatGPT or Claude?

Sign up at cotlet.dev, log in to DICE once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your DICE account through Cotlet, in their phone apps too.

What can ChatGPT do in DICE?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in DICE: weekly ticket sales report with returns and transfers; create an event draft with ticket types; add a ticket release when early bird sells out. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need a DICE API token?

No. Cotlet works in your own MIO account and does not use the Ticket Holders API, which is for DICE partners and needs a token generated in MIO (checked 11 Oct 2026).

Can my agent put an event on sale by itself?

It can create a draft and submit it, but DICE reviews every submitted event and decides at its sole discretion whether to promote it, so the agent cannot force an event live.

Does DICE have webhooks?

Not in its public API docs. Nothing tells an agent that early bird sold out or a fan returned a ticket, so run the agent on a schedule, for example a daily get_sales_summary pass over the shows on sale.

Can the agent read fans' personal data?

Only what your MIO role shows, such as ticket holder names on the door list. DICE's guidelines limit "All Customer Data" to messages about the event the fan bought for; marketing goes only to the Marketing Opt-ins list.

Is the MCP server different from the REST API?

Just the way in. MCP and REST carry the same 15 tools, inputs and answers, under one API key and one price. Agents call MCP; scripts and HTTP steps call REST.

Is Cotlet affiliated with DICE?

No. Cotlet is independent and not affiliated with DICE FM Holdings Ltd or Fever.

Can I use the DICE API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.