UFCalendar Fight API — MMA MCP server
RemoteAbout UFCalendar Fight API — MMA MCP server
UFCalendar Fight API skill is an installable guide for coding agents accessing MMA data through the UFCalendar API. It documents REST, SDK and MCP access to events, results, fighter records and related data.
Key features
- 01Endpoint and parameter reference
- 02REST, SDK and MCP access guidance
- 03Python and TypeScript quickstarts
- 04Client configuration examples
- 05Pagination, errors and rate-limit conventions
Use cases
- 01Look up event cards and results
- 02Retrieve fighter careers and round stats
- 03Check rankings history and judges' scorecards
- 04Configure an agent to access the API
MCP support
The skill explains how coding agents can use the UFCalendar MCP server at `https://api.ufcalendar.com/mcp`, alongside REST and SDK options. It supplies MCP client configuration examples.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.ufcalendar.com/mcpclaude mcp add --transport http com-ufcalendar-fight-api https://api.ufcalendar.com/mcp{"mcpServers":{"com-ufcalendar-fight-api":{"type":"http","url":"https://api.ufcalendar.com/mcp"}}}Open in Cursor{"servers":{"com-ufcalendar-fight-api":{"type":"http","url":"https://api.ufcalendar.com/mcp"}}}Open in VS Code{"mcpServers":{"com-ufcalendar-fight-api":{"type":"http","url":"https://api.ufcalendar.com/mcp"}}}{"mcpServers":{"com-ufcalendar-fight-api":{"serverUrl":"https://api.ufcalendar.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://api.ufcalendar.com/mcpAuth requiredTools
47This tool takes no parameters.
Details
From the project READMEUFCalendar Fight API — agent skill
An installable skill that teaches a coding agent how to reach the
UFCalendar Fight API — the MMA Fight Data API
behind our MCP server for UFC data
and MMA MCP server: UFC, PFL,
OKTAGON, BKFC and RIZIN events, full fight cards, results, per-round stats,
fighter careers, judges' scorecards, UFC rankings history since 2013 and
per-country broadcast rights — over REST, the two SDKs, or the MCP server at
https://api.ufcalendar.com/mcp.
Install
npx skills add UFCalendar/fight-api-skill
Or copy it in by hand:
| Agent | Where |
|---|---|
| Claude Code | .claude/skills/ufcalendar-fight-api/ (project) or ~/.claude/skills/ufcalendar-fight-api/ (global) |
| Cursor | paste SKILL.md into a rule under .cursor/rules/, keep references/ beside it |
| Codex | reference SKILL.md from AGENTS.md, keep references/ beside it |
The skill is plain Markdown — SKILL.md plus four reference files. Nothing
executes.
Contents
SKILL.md— access in 60 seconds, base URL and envelope, the endpoints that answer the common questions, the don'ts, and when to use MCP vs REST vs SDK.references/endpoints.md— every endpoint and parameter. Generated from the OpenAPI document; do not edit by hand.references/conventions.md— envelope, pagination, errors, rate headers, tier gates, webhook signature verification.references/mcp-clients.md— copy-paste config for Claude Code, Cursor, Codex, Claude.ai and ChatGPT.references/sdk.md— Python and TypeScript quickstarts.
Access
No free tier. A free 1-day trial (100 requests, no card, one per account)
self-serves at https://www.ufcalendar.com/account/api?trial=1; paid plans
start at $19/month. GET https://api.ufcalendar.com/v1/plans answers with no
credential at all, so an agent can evaluate the API before anyone signs in.
Odds are the UFCalendar consensus line only (no book identities; information only, not betting advice). Fighter images are Creative Commons and must be shown with their credit. Not affiliated with UFC, Zuffa, TKO or any promotion.
MIT licensed.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.