MCP server
Connect Claude, ChatGPT, Cursor, Perplexity, or any MCP client to Ticker's live event ticket market data. OAuth sign-in, one-click installs, tool reference.
Ticker serves its live event ticket market data (prices, demand, screening, alerts and event research) as a hosted MCP server. Any MCP client can query it with your Ticker account: Claude, ChatGPT, Cursor, Perplexity and others.
Getting started
Add the server URL to your client, then sign in with your Ticker account when the browser window opens. There are no API keys to create, copy or store.
https://api.findticker.com/mcpThe transport is Streamable HTTP. Every client is below, with a full walkthrough for the chat apps.
You need an account
There is no anonymous access. An account costs nothing at findticker.com and includes a tool-call allowance that renews every 30 days from the day you made the account; the paid plans raise it and open the deeper markets. What each plan includes is on findticker.com/plans.
Step-by-step guides
Connect ChatGPT
Add Ticker as a custom MCP server from ChatGPT's Plugins screen.
Connect Claude
Add Ticker from Claude's connector directory.
Connect Perplexity
Add Ticker as a remote custom connector.
Connect Cursor
One click adds the Ticker server to Cursor.
Connect Claude Code
Add Ticker with one command, then sign in from the terminal.
Clients
ChatGPT
Open ChatGPT plugins- Open Plugins, select the plus button, then Add custom MCP server.
- Name it Ticker, paste the server URL under Connection, choose OAuth, accept the warning, then select Create as a plugin.
- Install Ticker and sign in. In a new chat, type @ and pick Ticker.
If the menu has no Add custom MCP server, turn on Developer mode in Settings first.
Every step is in the ChatGPT walkthrough.
Claude
Any Claude plan, Free included. On Team and Enterprise an owner adds Ticker first.
Add to Claude- Press Add to Claude, or open Customize → Connectors, select + and find Ticker.
- Click Connect, then sign in to Ticker and approve access.
- In a chat, open + → Connectors and switch Ticker on.
Every step is in the Claude walkthrough.
Perplexity
Needs a paid Perplexity plan: Pro, Max or Enterprise.
- Open Plugins (or Customize → Connectors), select Add custom, then Add MCP connector, and choose Remote.
- Name it Ticker and paste the server URL into MCP server URL. Under Advanced, set Authentication to OAuth and Transport to Streamable HTTP, tick the box, then select Add.
- Select the Ticker card to sign in and turn it on, then name Ticker when you ask.
Every step is in the Perplexity walkthrough.
Cursor
Add to Cursor- Press Add to Cursor and confirm the install in Cursor.
- Open Customize → MCPs, switch Ticker on, and sign in to Ticker when asked.
- Ask about any event in Agent chat.
No button? Put these lines in ~/.cursor/mcp.json and restart Cursor:
{
"mcpServers": {
"ticker": { "url": "https://api.findticker.com/mcp" }
}
}Claude Code
-
Run this in your terminal (add
--scope userafteraddto have Ticker in every folder):claude mcp add --transport http ticker https://api.findticker.com/mcp -
Run
claude mcp login ticker(or/mcpinside Claude Code) and sign in to Ticker in your browser. -
Start Claude Code in that folder and ask about any event.
Already added Ticker on claude.ai? Sign in to Claude Code with that account and Ticker is there. Every step, with what the terminal prints, is in the Claude Code walkthrough.
Codex CLI
-
Run this in your terminal:
codex mcp add ticker --url https://api.findticker.com/mcp -
Run
codex mcp login tickerand sign in to Ticker in your browser. -
Start Codex and ask about any event.
VS Code (Copilot)
Add to VS Code- Press Add to VS Code, or run the command below in a terminal.
- Trust the server, then sign in to Ticker in your browser.
- In Copilot chat, open Configure Tools, check Ticker is on, and ask.
code --add-mcp "{\"name\":\"ticker\",\"type\":\"http\",\"url\":\"https://api.findticker.com/mcp\"}"Gemini CLI
-
Run this in your terminal:
gemini mcp add --transport http ticker https://api.findticker.com/mcp -
Restart Gemini CLI, run
/mcp auth tickerand sign in to Ticker. -
Ask about any event.
Any other MCP client
Any Streamable HTTP client takes the server URL. The minimal config most clients accept:
{
"mcpServers": {
"ticker": {
"url": "https://api.findticker.com/mcp"
}
}
}On first use the client follows the OAuth flow (Dynamic Client Registration and PKCE) and opens the findticker.com sign-in. There is no client secret to manage.
Authentication
The server uses OAuth 2.1 with PKCE. You never handle tokens by hand:
- Your client calls
/mcpand receives a401pointing at the server's OAuth metadata. - It registers itself (Dynamic Client Registration) and starts an authorization request.
- Your browser opens findticker.com to sign in and approve access.
- The client exchanges the result (with PKCE) for an access token and connects.
The access token is the server's own, separate from your findticker.com session; it is short-lived and refreshes on its own. Revoke access at any time by signing out of the connection in your client, or from your Ticker account settings.
Example prompts
| Prompt | Tools it reaches |
|---|---|
| Find NBA games in the next 30 days where resale prices dropped more than 20 percent this week but inventory is still tight. | screen_events, list_screen_columns |
| What is happening with the Oasis show at MetLife? Show me the price history and how demand has moved. | search_events, get_event_analytics, get_event_chart |
| Chart how Sabrina Carpenter's popularity rank has moved over the last three months. | get_performer_analytics |
| Save that screen as a view called Cheap and tightening, then show me what it has matched so far. | create_view, list_views, list_matches |
| Watch the three cheapest of those events and alert me when the median price falls another 10 percent. | watch_event, list_watchlist |
| Why did prices for that show move? Check the news and social coverage. | research_event |
Tool reference
The server exposes 26 tools. Each has a page with its parameters, generated from the server's own tool list: the tools reference. A tool name from before October 15, 2026 still answers: see Old names.
Screen and search
Find events, performers and venues, and learn what the predicate DSL accepts.
| screen_events | Finds and ranks upcoming events by price, demand and inventory. |
| search_events | Finds events by name, performer, venue or date, and gives their Ticker event ids. |
| list_screen_columns | Lists every column a screen or a View can name, with its meaning, its unit and the plan that includes it. |
| get_venue_schedule | Shows what is on at one venue, its sale dates and weather; finds venues and ids; or shows what each section costs. |
Event and performer analytics
The numbers for one event or performer, their history, the charts, completed sales, and the context behind a move.
| get_event_analytics | Shows every number for one event as it reads now, its sale windows, or with `range` how its numbers read on past dates. |
| get_event_chart | Charts one event over time: its prices and inventory, or its demand. |
| get_event_bundle | Reads one event's analytics, price series and sections in one call, as a short summary or as each part's rows. |
| get_performer_analytics | Shows one performer's numbers now: rank, prices across its events, X activity, or with `view` any of them by date. |
| get_sales | Shows completed sales and primary seats taken, as the Sales tab reads them: a list, a ranking, or per section. |
| research_event | Reads the event's research brief, as its page shows it: recent dated coverage of the event and its performers, with sources. |
Sections, seats and sellers
Inside one event: section prices and counts, the seats behind them, and how concentrated the sellers are, shown anonymously.
| get_event_sections | Shows one event's market by section: prices and tickets over time, the listings on sale, levels, one series across sections, or a map. |
| get_event_sections_live | Shows open seats per section of one event: now, at a past moment, one section or general admission over time, or the house over a window. |
| get_event_seats | Reads primary seats at one event: what is open now or at a past moment, and seats taken by section, and how that changed over time. |
| get_event_sellers | Shows one event's anonymous sellers: how concentrated they are, how they moved hour by hour, or chosen sellers' prices. |
Saved Views and Matches
Save a Screen so it runs on a schedule, say where it delivers, and read the events entering it.
| list_views | Lists your saved Views, whether each is on or paused, how many events each holds, where it delivers and its Digest. |
| create_view | Creates a View: a saved screen that tells you when events enter it, by email or a destination, with an optional Digest. |
| update_view | Changes a saved View: its name, predicate, delivery, destinations, paused state or Digest. |
| delete_view | Deletes a saved View and every Match it recorded, for good. |
| get_view_alert_preview | Shows what one View would have emailed in the last 24 hours under your current settings, and sends nothing. |
| list_matches | Lists the events that entered your Views, newest first, with whether an alert email carried each; or one Match in full. |
| list_destinations | Lists your alert destinations, such as Slack or Discord channels, and how many your plan holds. |
Watchlist
Follow single events and set what a watch fires on.
| watch_event | Stars one event and turns on its alerts, or changes the triggers of an event you starred already. |
| unwatch_event | Takes one event off your watchlist and stops its alerts. |
| list_watchlist | Lists the events you watch, with current prices, the triggers on each, and how many alerts each has made. |
Your account
Your plan, when it renews, and what is left of each allowance.
| get_account | Shows your plan and how much of each quota and limit is left in this billing cycle. |
Docs search
Answer a how-to question about the app, the API or the MCP server from these pages.
| search_docs | Finds the sections of these docs that best answer a how-to question, each with its page, heading, link and text. |
Skills
Once Ticker is connected, the free skills teach your assistant the screens and checks a seller runs with these tools.
Quotas
Ticker has five quotas. Each renews with your billing cycle, and one action spends exactly one of them, once. Feed requests applies only to an account that holds API keys.
| Quota | What spends one |
|---|---|
| MCP requests | Any MCP tool call except screen_events, research_event and the free list_screen_columns, get_account and search_docs |
| Screener runs | screen_events, a screen in the app's screener, and a POST /v1/screen on the API |
| Event research | A fresh research_event result, or a fresh research brief on an event page |
| Ask Ticker | One message to Ask Ticker in the app, including the tools it calls for that message |
| Feed requests | API feed reads with an API key, one unit for each event returned |
A cached research result spends nothing. A screen asked in plain language spends one
screener run, the same as the screen it produces. Views and stars, and alert destinations,
are limits on what you hold, not quotas you spend. get_account returns each quota with
what is used and left; your numbers are on
findticker.com/plans.
Limits
Some tools read the live seat log. Each call of one of these tools is heavy work for Ticker, so one account can run only a few at a time:
| Heavy tools |
|---|
get_event_sections_live, every view |
get_event_seats, every view |
get_event_sellers, views series and market |
Every other tool is light.
- Two heavy calls at a time per account. A third heavy call waits in line, first come
first served, for up to 30 seconds. When it runs after a wait, its result carries
_meta["ticker/queued_ms"], the time it waited. The answer itself is the same. - Past 30 seconds the call is refused as busy. Your heavy calls wait behind each other,
not behind other accounts' calls. When Ticker is busy overall, every caller's heavy calls
can wait briefly in one shared line, and past 30 seconds they are refused as
busy_global. - Ceilings per account: 120 heavy calls a minute and 3,000 an hour; 600 light calls a minute and 10,000 an hour. Every plan has the same ceilings. Plans differ in their allowance for the billing cycle, not in these numbers.
- One answer is at most 40,000 characters. A longer one comes back cut at the head of
its list, with
meta.truncated,meta.returned_rowsofmeta.total_rows, andmeta.next, the call that reads on.
A refused call is a tool error whose text is JSON:
{
"error": "busy",
"message": "Ticker is busy with this account's earlier calls of this kind. Wait 6 seconds, then call again. Send these calls one at a time, not all at once.",
"retry_after_seconds": 6
}error | Meaning | What to do |
|---|---|---|
busy | The account already has heavy calls running and the line did not clear in 30 seconds. | Wait retry_after_seconds, then call again. Send heavy calls one at a time. |
busy_global | Ticker as a whole is running as many heavy calls as it can, and the shared line did not clear in 30 seconds. | Wait retry_after_seconds, then call again. |
rate_limited | The account reached a per-minute or per-hour ceiling. | Wait retry_after_seconds, then call again. |
A refused call does not count against your plan's allowance.
Researching many events at once? Send the calls one at a time, not in parallel: the answers come back as fast, and none is refused. For bulk research across hundreds of events, contact us about the API. These are current limits, not an SLA.
Troubleshooting
The client never asks me to sign in
Remove the server and add it again, checking the URL is exactly the one above. The sign-in prompt comes from the client the first time it connects.
"The access token is invalid or expired"
Your client normally refreshes tokens on its own. If the error persists, disconnect and reconnect the server to sign in again.
"Payment required" or a plan error when calling tools
Your account does not currently include that reading. See what each plan includes on the plans page, then reconnect.
"You have used all … on your plan"
Your plan's allowance renews on the date shown in
Settings. Discovery calls like list_screen_columns do
not count against it.
"Ticker is busy with this account's earlier calls"
Your assistant sent more heavy calls at once than the account can run. Wait the seconds the message names and ask again, one event at a time. See Limits.
Connected, but tools are missing from the client's list
Some clients cache the tool list. Reconnect the server (or restart the client) to refresh it.
Security contact
Connections are authorized per user over OAuth 2.1 (PKCE required); access tokens are short-lived and refresh tokens rotate on use. The server only ever sees your Ticker data: no marketplace accounts, no payment credentials.
Ticker data is for research, pricing and market analysis.
Found a vulnerability? Email alim@findticker.com with reproduction steps. We read every report.
Ticket market data API and MCP
Ticker is ticket market data: primary and resale prices, price history and market activity, in the app, your AI or the API.
Connect ChatGPT
Add Ticker as a custom MCP server from ChatGPT's Plugins screen. Step by step, with the current ChatGPT menu names (checked 2026-11-07).