Sports Context Protocol
Give Claude or Cursor a self-updating sports operations context layer so golf (and future sport profiles) agents answer with course, rules, and session memory instead of generic guesses.
Overview
Sports Context Protocol is a Build-phase MCP server that supplies a self-learning operational context layer for AI sports agents, starting with a golf profile.
What is this MCP server?
- Self-learning operational context layer tailored to AI sports agents
- Profile 001 ships golf-specific context (extensible to more sports profiles)
- stdio MCP via npx sports-context-protocol (v0.1.2)
- npm registry package with no secret env vars in server.json
- Server version 0.1.2
- Profile 001: golf
- Transport: stdio via npx
What problem does it solve?
Sports AI demos sound smart until they lack live operational context about the game, course, or athlete session you are actually building for.
Who is it for?
Indie builders creating golf or sports copilots who want a dedicated context MCP alongside their code agent.
Skip if: Teams with no sports product angle or anyone who only needs generic web search without domain memory.
What do I get? / Deliverables
After you add the MCP server, your agent can ground answers in sports-specific context profiles instead of generic LLM knowledge.
- stdio MCP connection to sports-context-protocol
- Golf profile 001 context available to the agent
- Foundation for additional sport profiles in the same protocol
Recommended MCP Servers
Journey fit
Sports agents are built during the product phase when you wire domain MCP tools into your coding agent stack. Agent-tooling is the canonical shelf for MCP servers that extend what your AI assistant can know and do at runtime.
How it compares
Domain context MCP for sports agents, not a general web browser or database connector.
Common Questions / FAQ
Who is Sports Context Protocol for?
Solo and indie developers building AI sports assistants—especially golf-first products—who use Claude Code, Cursor, or similar MCP clients.
When should I use Sports Context Protocol?
During Build when you are wiring agent-tooling and need structured, self-updating sports operational context instead of hard-coded prompts.
How do I add Sports Context Protocol to my agent?
Install via npx sports-context-protocol with stdio transport per the MCP registry entry and point your client at the published npm package (v0.1.2).