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. It covers the same endpoints as the REST API, including three discovery tools that answer with no sign-in at all.

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.

Every account gets a free 1-day trial: 100 requests, no credit card, one per account, and it starts automatically the first time an agent authorizes. After that, 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?

No, and they never will be. The Fight API carries no betting data on any plan or through any tool. Model win probabilities are published as informational model output, 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 1-day trial · 100 requests · no credit card. Paid plans from $19/mo for 30,000 requests, cancel anytime.

Start free trial 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. The free 1-day trial — 100 requests, no card — starts automatically the first time you authorize, so there is 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

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 tool wraps a documented REST endpoint, and one tool call counts as one request against your plan.

Tool	What it does	Access
`get_plans`	List the UFCalendar Fight API plans, their monthly request quotas and per-minute limits, and the terms of the no-card trial. 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).	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
`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. Cursor paginated.	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.	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
`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.	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.	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.	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.	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.	Read
`get_predictions_upcoming` `GET /v1/predictions/upcoming`	UFCalendar model win probabilities for upcoming UFC bouts, corner-stamped so a probability is never shown against the wrong pair. 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. Filter by name, promotion or a minimum number of fights.	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. Commission records only.	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.	Read
`get_venue` `GET /v1/venues/{id}`	Fetch one venue by id: name, city, region, country, capacity, coordinates and IANA time zone.	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.	Read
`create_webhook_endpoint` `POST /v1/webhook-endpoints`	Register an https endpoint to receive signed webhooks (event announced, fight result, card changed, event completed). The signing secret is returned ONCE — store it before the reply is discarded. At most 3 active endpoints per account.	Write
`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.	Write
`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.	Write

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.

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.

Plan	Price	Requests / month	Requests / minute
Trial	Free	100	30	Start free trial
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
Enterprise	Contact us	5,000,000	1,200	api@ufcalendar.com

The trial runs 24 hours and 100 requests, needs no card and is once per account. There is no permanent free plan.

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 — no betting odds anywhere, 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. It covers the same endpoints as the REST API, including three discovery tools that answer with no sign-in at all.
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?: Every account gets a free 1-day trial: 100 requests, no credit card, one per account, and it starts automatically the first time an agent authorizes. After that, 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?: No, and they never will be. The Fight API carries no betting data on any plan or through any tool. Model win probabilities are published as informational model output, 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 and rankings history — each with its own endpoints, sample responses and code.

UFC Schedule API UFC Results API UFC Stats API UFC Rankings API UFC Scorecards API Explore the UFC API Explore the PFL API Explore the OKTAGON API Explore the BKFC API Explore the RIZIN API 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