Fitness
SportsStack MCP connector
The SportsStack connector brings events, odds, markets, futures, injuries, players, leagues, and news into Claude, ChatGPT, Cursor, and any MCP client, so your team can ask questions of live sports records inside their own access, with every call logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect SportsStack to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SportsStack once
-
Open Connections, choose Add connection, and pick SportsStack.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a SportsStack API key. One person generates a token in SportsStack and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect SportsStack to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect SportsStack to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect SportsStack to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect SportsStack to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with SportsStack through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Content
Draft the morning odds roundup
Pull tonight's SportsStack events, the current odds on each market, and the latest news into a draft your editors can finish before it goes out.
-
Trading
Check a market before moving a line
Ask for every odd on a SportsStack market, the related futures, and any injury reported since yesterday, then decide with the whole picture in front of you.
-
Analytics
Track injuries against the upcoming slate
Match SportsStack injury timelines to the events scheduled this week and flag the games where a key player's status is still open.
-
Support
Answer a question about a finished game
Pull the SportsStack scoreboard and event details for a game a customer is asking about, so the reply carries the actual score and timing rather than a guess.
-
Data
Reconcile player and team identifiers across feeds
Use SportsStack mappings and global identities to confirm that the player in your warehouse is the same player in the odds feed before a report goes out.
-
Marketing
Build a parlay for a weekend promotion
Start from SportsStack betting recommendations, pick the legs, and create the parlay odd that the promotion will feature, with the person who made it named in the log.
Try asking
- “Show today's SportsStack market odds for the main slate.”
- “Which players appear in this week's SportsStack injury timelines?”
- “Summarize the latest SportsStack betting recommendations for football futures.”
AI tools
SportsStack tools for your AI agents
61 tools are ready to call through Elaichi's MCP endpoint the moment you connect SportsStack, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting SportsStack gets you
6 screens from the product, each doing one job for your SportsStack account.
The agent
Ask about markets, get live answers.
Type a question in plain language and read it back from SportsStack records.
- odds
- markets
- futures
- injuries
Ask Elaichi to work across your apps.
Show today's SportsStack market odds for the main slate.
Which players appear in this week's SportsStack injury timelines?
Summarize the latest SportsStack betting recommendations for football futures.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor, one endpoint.
Reach SportsStack from any MCP client over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
61 SportsStack tools, no custom code.
Odds, futures, markets, injuries and news, each with named resources and methods.
- List all SportsStack stat types
- List all SportsStack futures
- Get single SportsStack future by ID
- List all SportsStack markets
Toolboxes
Every team gets its own toolbox.
Curate one SportsStack toolbox for traders, another for editorial, another for analytics.
- Trading
- Editorial
- Analytics
- Risk
Shared connections
Share odds access, never the credential.
See who connected each SportsStack account and which teams and members use it.
- Trading EMEA
- Editorial
- Analytics
- Risk
Audit log
Answer who pulled which odds, exactly.
Every SportsStack call lands append only with time, actor, action, type and resource.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships.
Fetch SportsStack injuries, group them, draft a digest, approve, post it back.
SportsStack digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch odds
SportsStack
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
SportsStack
Queued
Collections and dashboards
Connector health, counted not generated.
Four metrics, 14 days of SportsStack records created, split by team, refreshed on schedule.
SportsStack health
Refreshed 4 minutes ago · every 15 minutes · from the odds collection
Odds
1,284 ↓ 12%
Markets
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Odds created
Last 14 days
By team
Share of activity
Trading EMEA 34%
Editorial 27%
Analytics 21%
Risk 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect SportsStack to Claude?
Two steps. In Elaichi, choose SportsStack and paste in your SportsStack API key, which is all the sign-in asks for, since there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the Elaichi endpoint, https://api.elaichi.ai/mcp. Sign in as yourself and SportsStack is ready to ask questions of.
Does SportsStack work with ChatGPT and Cursor as well as Claude?
Yes. SportsStack is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is what Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent connect to. You do not set SportsStack up again for each client, and each person signs in as themselves wherever they use it.
What can an AI agent actually do with my SportsStack data?
With SportsStack connected, an agent can look up events, scoreboards, leagues, and players, pull the current odds on a market or a future, list injuries and their timelines, read the latest news, and check the mappings that tie identifiers together across feeds. It can also pull betting recommendations and create a parlay odd when someone asks for one. Because SportsStack has a lot of ways to answer, short concrete asks such as "odds on tonight's Lakers game" get better results than a long paragraph.
Does connecting SportsStack give the AI everything in my account?
No. Access to SportsStack follows the API key and the person who signed in to Elaichi, so an agent can only reach the leagues, markets, and records that person could already reach. Elaichi can narrow that further, for example to reading only or to a subset of what SportsStack offers, but it can never widen it beyond what the account allows.
Can I stop an agent from deleting or changing things in SportsStack?
Yes. Restrictions in Elaichi apply per action, so you can leave SportsStack read only for a team by blocking the one action that writes, creating a parlay odd, while lookups of events, odds, injuries, and news keep working. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to a SportsStack connection when someone leaves?
Offboarding that person in Elaichi ends their SportsStack access at once, across every client they used. If they were using a shared SportsStack connection, it keeps working for everyone else on the team. If you want SportsStack gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put SportsStack in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.