Is there an MCP server?

Yes. The UFCalendar Fight API runs a hosted MCP server at https://api.ufcalendar.com/mcp over Streamable HTTP. Add it as a custom connector in Claude.ai or ChatGPT, or register it in Claude Code, Cursor or Codex with an API key. Setup, the tool table and an honest comparison of the alternatives live on the MCP server pages.

Both work. Chat clients are easiest with OAuth — sign in with your UFCalendar account and approve the connector. Coding agents and servers are easiest with an API key sent as a bearer token, and a terminal with no browser can mint one through the device flow. Either way, access is revocable from your account at any time.

Yes, to start: every account gets the free plan — 1,000 requests a month, no credit card, never expires — and it works the first time an agent authorizes. Paid plans start at $19 a month for 30,000 requests. Three discovery tools — plans, promotions and how to connect — answer with no credential at all.

Are betting odds included?

Yes, as one consensus line per bout: the mean across the sportsbooks we track, with the opening and closing line, on every plan and through the get_fight_odds and get_event_odds tools. Movement history (get_odds_history) is Pro and up. Book identities are never exposed. Odds and model win probabilities are information only, not betting advice.

How are tool calls metered?

One tool call is one request, metered exactly like a REST call: it counts against your monthly quota and your per-minute limit. Both are hard caps rather than overage billing, so an agent that loops gets a 429 and never a surprise bill.

Anything that speaks MCP over Streamable HTTP: Claude.ai and the Claude apps, Claude Code, ChatGPT, Cursor, Codex, Cline, and custom agents built on any MCP SDK. Without MCP, the REST API works from any language, with typed Python and TypeScript clients.

UFCalendar Fight API

Fight API for AI agents

A hosted MCP server, an OpenAPI 3.1 spec, Python and TypeScript clients and an installable agent skill — so an agent can find UFCalendar's fight data, judge whether it fits, and start querying UFC, PFL, OKTAGON, BKFC and RIZIN cards in under a minute. UFCalendar is independent and not affiliated with UFC, Zuffa or TKO.

Free plan: 1,000 requests/month, no card, never expires. Paid plans from $19/mo for 30,000 requests, cancel anytime.

Get a free key Read the docs Pricing & plans

MCP endpoint https://api.ufcalendar.com/mcp

Connect in 60 seconds

Three doors into the same data: sign in from a chat client, paste a key into a coding agent, or call the REST API directly.

1 · Sign in from Claude.ai or ChatGPT

Add a custom connector with the URL below, sign in with your UFCalendar account and approve the request. Every account is on the free plan — 1,000 requests a month, no card — so it works the moment you authorize, with no key to copy anywhere.

Connector URL — Claude.ai, ChatGPT or any MCP client

https://api.ufcalendar.com/mcp

2 · API key in a coding agent

Claude Code, Cursor and Codex all speak Streamable HTTP. Put your key in UFCALENDAR_API_KEY and register the server once.

Claude Code

claude mcp add --transport http ufcalendar https://api.ufcalendar.com/mcp \
  --header "Authorization: Bearer $UFCALENDAR_API_KEY"

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "ufcalendar": {
      "url": "https://api.ufcalendar.com/mcp",
      "headers": { "Authorization": "Bearer ${UFCALENDAR_API_KEY}" }
    }
  }
}

Codex — ~/.codex/config.toml

[mcp_servers.ufcalendar]
url = "https://api.ufcalendar.com/mcp"
http_headers = { Authorization = "Bearer ${UFCALENDAR_API_KEY}" }

No browser on that machine?

Terminals and headless agents can use the device flow: ask for a code, open the verification page on any device, paste the code, then poll for the token.

Device flow

# Form-encoded (RFC 8628 §3.4) or JSON — both are accepted.
curl -s -X POST https://www.ufcalendar.com/api/auth/device/code \
  -d 'client_id=claude-code'
# {"device_code":"...","user_code":"WXYZ-1234",
#  "verification_uri":"https://www.ufcalendar.com/device", ...}

# Open https://www.ufcalendar.com/device, paste WXYZ-1234, approve.

curl -s -X POST https://www.ufcalendar.com/api/auth/device/token \
  -d 'client_id=claude-code' \
  -d 'grant_type=urn:ietf:params:oauth:grant-type:device_code' \
  -d 'device_code=...'

3 · REST and the SDKs

No MCP client involved: the same endpoints are a plain REST API over HTTPS with bearer auth, with typed clients for Python and TypeScript and a machine-readable spec.

Python

pip install ufcalendar

TypeScript

npm i @ufcalendar/sdk

curl

curl -H "Authorization: Bearer $UFCALENDAR_API_KEY" \
  "https://api.ufcalendar.com/v1/events?org=ufc&limit=3"

PyPI · npm · OpenAPI 3.1 · llms.txt · llms-full.txt

Tools the MCP server exposes

Every data tool maps to a documented REST endpoint, and one tool call counts as one request against your plan.

Tools the MCP server exposes
Tool	What it does	Access
`get_plans`	List the UFCalendar Fight API plans, their monthly request quotas and per-minute limits, including the free plan (1,000 requests a month, no card). Answers "what does this cost" without a credential.	ReadNo sign-in
`list_orgs` `GET /v1/orgs`	List the promotions the UFCalendar Fight API covers, with per-org capability flags (stats, rounds, rankings, broadcasts, predictions, scorecards, odds). Odds are the UFCalendar consensus line: information only, not betting advice.	ReadNo sign-in
`how_to_connect`	Explain how to authenticate against the UFCalendar Fight API from this MCP server: an API key bearer token, or signing in with a UFCalendar account. Returns the URLs to do it.	ReadNo sign-in
`get_org` `GET /v1/orgs/{slug}`	Fetch one promotion by slug (ufc, pfl, oktagon, bkfc or rizin): name, short name, country, website and its capability flags (stats, rounds, rankings, broadcasts, predictions, scorecards, odds; odds are information only, not betting advice). list_orgs returns the same rows for every promotion without a credential.	Read
`get_division` `GET /v1/orgs/{slug}/divisions/{division}`	One weight class in one promotion: the current rankings board when the promotion publishes one, upcoming bouts booked at that weight, the most recent results and the active roster by recency. The division-page answer in one call.	Read
`list_events` `GET /v1/events`	List fight cards by promotion, status and date range. A bare call returns the upcoming schedule, soonest first; pass order=desc for the archive, newest first. Filter to title cards or PPVs with is_title_card / is_ppv, and pass include=headline for each card's main event (and its result once fought) in the same call. Cursor paginated.	Read
`get_next_event` `GET /v1/events`	The single next upcoming card for one promotion, or across all of them: the soonest event that has not finished. For UFC, developmental sub-series cards (Dana White's Contender Series, Road to UFC) are skipped while a numbered card or Fight Night is booked; pass skip_series=false to include them. Pass include_card=true to get the full bout list in the same metered call.	Read
`get_event_card` `GET /v1/events/{idOrSlug}`	Fetch one event by slug or id with its complete bout order, both corners, venue, broadcast listings and results when the card has been fought. Pass include=eta for per-bout estimated start times and include=odds for each bout's current UFCalendar consensus odds line (information only, not betting advice).	Read
`get_event_changes` `GET /v1/events/{idOrSlug}/changes`	The audit trail for one card: bouts added or cancelled, opponents swapped, start times moved, fighter profiles merged — newest first.	Read
`list_changes` `GET /v1/changes`	The cross-event change feed, newest first: bouts added, cancelled or reinstated, opponents swapped, start times or venues moved, fighter profiles merged — across every covered promotion or one of them, since a date (default the last 90 days). The same audit trail webhooks deliver, for agents that poll instead.	Read
`how_to_watch` `GET /v1/events/{idOrSlug}/watch`	Who airs one event, country by country: the promotion's rights deals merged with the event's own confirmed broadcast listings, with provider, kind (tv, stream, ppv…), link and a worldwide row. Pass a two-letter country code to get that market plus worldwide. Series-aware, so a Contender Series card shows its own deal, not the numbered-card one.	Read
`get_event_storylines` `GET /v1/events/{idOrSlug}/storylines`	The talking points of one card, computed from the record: title fights and title eliminators, the closest bout by UFCalendar's model, rematches and trilogy deciders, who is on a streak, who is debuting or returning from a long layoff, the ranked fighters and champions on the card, nations represented, the tallest and longest-reach fighters and the fastest career finish on the bill.	Read
`get_pickem_splits` `GET /v1/events/{idOrSlug}/pickem`	How the UFCalendar community is picking each bout on one card: picks for each corner, the total and the percentage, in card order. Crowd sentiment from our own pick'em game, not a market and not a forecast.	Read
`get_event_odds` `GET /v1/events/{idOrSlug}/odds`	The UFCalendar consensus odds line for every bout on one card, in card order: the current line, the opening line, the closing line once a bout is settled, and how far the market moved since opening, each with how many sportsbooks backed it, plus every bout's prop markets (method of victory, total rounds, goes the distance). Unpriced bouts are listed with nulls. Book identities are never exposed. Information only, not betting advice.	Read
`get_fight_odds` `GET /v1/fights/{id}/odds`	The UFCalendar consensus odds line for one bout: the current line, the opening line, the closing line once the bout is settled, and the movement since opening in implied-probability points, each point with its American and decimal price, implied and margin-removed probability and how many sportsbooks backed it. Also the prop markets: method of victory per corner (KO/TKO, submission, decision), total rounds over/under per line and whether it goes the distance. Book identities are never exposed. Information only, not betting advice.	Read
`get_odds_history` `GET /v1/fights/{id}/odds/history`	Every UFCalendar consensus odds point recorded for one bout, oldest first: the line-movement series, with how many sportsbooks backed each point. A point is stored only when the line moves. Narrow with from/to dates; cursor paginated. Pro plans and up. Information only, not betting advice.	ReadPro+
`get_fight` `GET /v1/fights/{id}`	Fetch one bout by id. Pass include=stats for per-fight totals, include=rounds for round-by-round statistics, include=scorecards for the official judges’ cards, include=odds for the current UFCalendar consensus odds line (the closing line once the bout is settled) (information only, not betting advice).	Read
`get_fight_stats` `GET /v1/fights/{id}/stats`	Per-fight totals for both corners of one bout (strikes by target and position, takedowns, knockdowns, control and position time), each with UFCalendar fantasy points and their category breakdown, plus data-quality flags in meta.quality (rounds present, position data present, whether the round sums match the totals).	Read
`find_fights` `GET /v1/fights/search`	THE tool for last/first/most-recent questions — search completed bouts across UFCalendar's launch promotions by title fight, finish method (ko, sub, dec, finish), division, fighter, winner, main-event only and date range, newest first by default. One call answers "the last title fight to end by knockout"; never page the schedule for it. At least one narrowing filter is required; 25 rows per page, 10 pages deep.	Read
`search` `GET /v1/search`	Typeahead search across fighters and events in one call. Use it to turn a name a user typed into a slug you can pass to the other tools.	Read
`search_fighters` `GET /v1/fighters`	Search the fighter roster by name, nationality or promotion. Cursor paginated. Returns identity fields; use get_fighter for the full record.	Read
`get_fighter` `GET /v1/fighters/{idOrSlug}`	Fetch one fighter by slug or id: bio, record, career statistics and freely licensed portraits. Pass include=history for the full multi-promotion career timeline, include=stats, include=rankings or include=power_index, include=bonuses for the UFC bonus ledger, and include=credentials for grappling and wrestling pedigree, gyms and coaches (sourced, confidence-graded). Always carries next_fight and last_fight.	Read
`compare_fighters` `GET /v1/compare`	Head-to-head in one call: both bios and career statistics, strike location and position mix, current win streaks, previous meetings, common opponents with each result, the booked bout between them if one exists, UFCalendar's model win probability for it and the Power Index ratings. The tale-of-the-tape tool.	Read
`get_rankings` `GET /v1/rankings/{org}`	The official rankings board for one promotion, point-in-time: pass a date to read the board as it stood that day. Rank 0 is the champion. Pass a division to narrow it. Each entry comes with movement against the previous snapshot (is_new for a debut), and meta names the previous and next snapshot dates.	Read
`get_champions` `GET /v1/champions`	Every current champion across the promotions the API covers, with the division and the snapshot date the board was published. Pass org (e.g. "ufc") and/or division (e.g. "lightweight") to narrow it.	Read
`get_power_index` `GET /v1/power-index/{org}`	The UFCalendar Power Index board for one promotion — our own rating engine, refreshed hourly, with peak rating and fights rated. Pass view=movers for the biggest risers over a window, view=peaks for all-time peak ratings, division= to narrow.	Read
`get_matchmaker` `GET /v1/matchmaker/{org}`	UFCalendar's matchmaker: the fights worth making in one promotion, scored for rank proximity, momentum, competitiveness and story (rematches, eliminators), per division or across the roster. Our own engine over rankings, Power Index and recent form — not a list of booked bouts. Runs without the website's style-clash (Fight DNA) factor, so scores can differ slightly from ufcalendar.com.	Read
`whos_next` `GET /v1/matchmaker/next/{fighter}`	For one fighter: the most sensible next opponents by UFCalendar's matchmaker, with the model win probability for each pairing and the score behind it, plus the bout already booked if there is one. Runs without the website's style-clash (Fight DNA) factor, so scores can differ slightly from ufcalendar.com.	Read
`get_leaderboard` `GET /v1/stats/leaders`	One statistical leaderboard for one promotion from UFCalendar's Record Book rollup — career, single-fight, single-round, division or event boards across 48 metrics (wins, finishes, significant strikes, takedowns, control time, finish rate and more), optionally narrowed to a division, a country or active fighters. Ranked, with the sample size behind each value.	Read
`get_record_book` `GET /v1/stats/record-book`	The Record Book for one promotion in one call: the top rows of every leaderboard, grouped by category — the all-time and single-night records an agent quotes. Narrow by division, country, active fighters or one scope.	Read
`get_year_stats` `GET /v1/stats/years/{year}`	One calendar year of a promotion (or all covered promotions) in numbers: events and title fights, finish methods and busiest divisions, the fastest finishes, the biggest upsets and Power Index climbers, the busiest fighters, host countries and the most-used judges.	Read
`get_predictions_upcoming` `GET /v1/predictions/upcoming`	UFCalendar model win probabilities for upcoming UFC bouts, published about three weeks out and repriced at least weekly. Corner-stamped, so a probability is never shown against the wrong pair. Pass event= to narrow to one card. Informational model output, not betting advice.	Read
`get_broadcast_rights` `GET /v1/broadcast-rights/{org}`	Who airs one promotion in each country: provider, kind and link. Pass a country code to narrow it to that market plus the worldwide row.	Read
`list_judges` `GET /v1/judges`	The judge directory with career aggregates: cards turned in, rounds scored, 10-8s, split cards and lone dissents, plus the league-wide baseline rates in meta.league. Filter by name, promotion or a minimum number of fights.	Read
`get_judge` `GET /v1/judges/{id}`	One official's career aggregates by id: fights and rounds scored, rounds scored 10-8 or wider, three-judge cards that came back split, lone dissents, first and last date scored, and the promotions worked. Same shape as a list_judges row; use get_judge_scorecards for the cards themselves.	Read
`get_judge_scorecards` `GET /v1/judges/{id}/scorecards`	Every official card one judge has turned in, newest first: per-round points, card totals, decision type and point deductions. Each row flags lone dissents and split panels and shows the colleagues' totals. Commission records only.	Read
`list_referees` `GET /v1/referees`	The referee directory across the covered promotions, busiest first: bouts worked, promotions, first and last bout, finish rate, how their bouts ended (KO/TKO, submission, decision, other) and average fight time. Filter by name or promotion. The referee id is a slug of the name.	Read
`get_referee` `GET /v1/referees/{slug}`	One referee's career aggregates by slug (e.g. herb-dean): bouts worked per promotion, first and last bout, finish rate, method breakdown and average fight time. Same shape as a list_referees row; use get_referee_fights for the bouts themselves.	Read
`get_referee_fights` `GET /v1/referees/{slug}/fights`	Every settled bout one referee worked in the covered promotions, newest first, with both corners, the result and the event. Cursor paginated.	Read
`list_split_decisions` `GET /v1/scorecards/splits`	Completed bouts decided on split or majority cards, newest first, with every judge's official card and the dissenting judge named — commission records only, across covered promotions or one of them, in a date range. Facts as filed; UFCalendar adds no verdict of its own.	Read
`get_coverage` `GET /v1/coverage`	What the database holds for each covered promotion, year by year: events, settled bouts and the share of them with per-fight stats, round-by-round stats, official commission scorecards and a UFCalendar consensus odds line (information only, not betting advice), plus when the latest result landed. Computed from the data, refreshed every 30 minutes.	Read
`get_usage` `GET /v1/usage`	How many requests the calling account has used this month, the plan limit, the per-minute limit and when the counter resets — and, on an owner-granted trial, when the trial ends (trial_ends_at).	Read
`get_venue` `GET /v1/venues/{id}`	Fetch one venue by id: name, city, region, country, capacity, coordinates and IANA time zone.	Read
`search_venues` `GET /v1/venues`	Find arenas and venues that have hosted a covered promotion, by name, city or country. Returns id, name, city, region, country, time zone and capacity; pass the id to get_venue_events for what was fought there.	Read
`get_venue_events` `GET /v1/venues/{id}/events`	Every covered event held at one venue, newest first — upcoming cards on top, then the history. Same filters and row shape as list_events (status, from, to, order, cursor).	Read
`search_articles` `GET /v1/articles`	Search UFCalendar's own editorial archive — previews, recaps, investigations, fighter-pay and technique pieces — by keyword or tag, newest first, in any of the 13 site languages. Returns title, summary, tags, date and the canonical URL; pass the slug to get_article for the body. Betting editorial is not served.	Read
`get_article` `GET /v1/articles/{slug}`	One UFCalendar article by slug: full body in Markdown (client widgets removed), title, summary, author, tags and publication date, in the requested language when a translation exists (English otherwise). Betting editorial is not served.	Read
`get_calendar_feed_url` `GET /v1/calendar/{org}.ics`	The three subscribable ICS calendar feed URL templates for one promotion — per event, per card section, or per bout at its estimated start — with a <your-api-key> placeholder where the key goes. Returns URL templates only, never the caller's credential; the human pastes the finished URL into their calendar app.	Read
`list_webhook_endpoints` `GET /v1/webhook-endpoints`	List the signed webhook endpoints registered on the calling account, with the event kinds each one subscribes to.	ReadPro+
`create_webhook_endpoint` `POST /v1/webhook-endpoints`	Register an https endpoint to receive signed webhooks (event announced, fight result, card changed, event completed, odds moved: the UFCalendar consensus odds line on an upcoming bout moved 5+ points or the favourite flipped; information only, not betting advice). The signing secret is returned ONCE — store it before the reply is discarded. At most 3 active endpoints per account.	WritePro+
`rotate_webhook_secret` `POST /v1/webhook-endpoints/{id}/rotate-secret`	Replace the signing secret of one webhook endpoint. The old secret stops verifying immediately, so update the receiver first. The new secret is returned once.	WritePro+
`delete_webhook_endpoint` `DELETE /v1/webhook-endpoints/{id}`	Permanently remove one webhook endpoint from the calling account. Deliveries to it stop and its delivery history is dropped.	WritePro+

Names and descriptions appear exactly as the server advertises them to a client, in English — that is the text your agent reads when it picks a tool.

Who it's for

Built for indie developers, side projects and small teams. Whether you're building a fantasy app, a stats site, a Discord bot or an analytics project, our plans are priced for you. We don't sell enterprise contracts, and we don't plan to.

Plans for agents

One key covers every promotion. Quotas are hard caps with no overage billing, so an agent stuck in a loop gets a 429 instead of an invoice.

Plans for agents
Plan	Price	Requests / month	Requests / minute
Free	Free	1,000	10	Get a free key
Hobby	$19/mo	30,000	60	Choose plan
Pro	$49/mo	200,000	300	Choose plan
Business	$149/mo	1,000,000	600	Choose plan

The free plan gives 1,000 requests a month at 10 a minute, needs no card and never expires.

Machine-readable, no credential required: GET /v1/plans · oauth-authorization-server · oauth-protected-resource

Install the skill

The UFCalendar agent skill teaches a coding agent the base URL, the auth header, the endpoints worth calling and the rules that matter: odds are one anonymised consensus line and never betting advice, and the image credit line is required by the licence.

Agent skill

npx skills add UFCalendar/fight-api-skill

https://github.com/UFCalendar/fight-api-skill

Questions

Is there an MCP server?: Yes. The UFCalendar Fight API runs a hosted MCP server at https://api.ufcalendar.com/mcp over Streamable HTTP. Add it as a custom connector in Claude.ai or ChatGPT, or register it in Claude Code, Cursor or Codex with an API key. Setup, the tool table and an honest comparison of the alternatives live on the MCP server pages.
OAuth or an API key?: Both work. Chat clients are easiest with OAuth — sign in with your UFCalendar account and approve the connector. Coding agents and servers are easiest with an API key sent as a bearer token, and a terminal with no browser can mint one through the device flow. Either way, access is revocable from your account at any time.
Is it free?: Yes, to start: every account gets the free plan — 1,000 requests a month, no credit card, never expires — and it works the first time an agent authorizes. Paid plans start at $19 a month for 30,000 requests. Three discovery tools — plans, promotions and how to connect — answer with no credential at all.
Are betting odds included?: Yes, as one consensus line per bout: the mean across the sportsbooks we track, with the opening and closing line, on every plan and through the get_fight_odds and get_event_odds tools. Movement history (get_odds_history) is Pro and up. Book identities are never exposed. Odds and model win probabilities are information only, not betting advice.
How are tool calls metered?: One tool call is one request, metered exactly like a REST call: it counts against your monthly quota and your per-minute limit. Both are hard caps rather than overage billing, so an agent that loops gets a 429 and never a surprise bill.
Which clients work?: Anything that speaks MCP over Streamable HTTP: Claude.ai and the Claude apps, Claude Code, ChatGPT, Cursor, Codex, Cline, and custom agents built on any MCP SDK. Without MCP, the REST API works from any language, with typed Python and TypeScript clients.

More Fight API pages

One page per job: schedules, results, per-round statistics, rankings history, judges' scorecards and consensus odds, each with its own endpoints, sample responses and code.

UFC schedule UFC fight results UFC fight stats UFC rankings history UFC scorecards UFC odds UFC API PFL API OKTAGON API BKFC API RIZIN API MCP server for UFC data MMA MCP Server MMA API comparison Build an MMA app How do I add UFC data to Claude or ChatGPT with MCP?Code guides Pricing & plans

UFCalendar is an independent publication, not affiliated with UFC/Zuffa/TKO, PFL, OKTAGON MMA, BKFC, RIZIN FF or any promotion. Organization names are used to describe the data. Terms of service · Refund Policy