Cursor

1. Get a token

Register at the API Locker to generate an RSC_token. New accounts include a 30-day free trial.

2. Put it in your environment

Cursor reads the token from the RSC_TOKEN environment variable rather than storing it in a config file. Add it to your shell profile (~/.zshrc, ~/.bashrc) or your secret store:

export RSC_TOKEN='your-token-here'

Cursor is a GUI app, and it inherits the environment of whatever launched it: started from the dock, it may never see a variable you exported in a terminal. After setting the variable, launch Cursor from a fresh terminal (cursor .) so it picks the variable up.

Never paste your raw token into an agent chat. Anything you type into a conversation may be persisted in a transcript, synced to a vendor, or written into a log you don't control. Set the environment variable and let Cursor reference it — no step on this page needs the token's value to appear anywhere. If a token has already been pasted somewhere it shouldn't be, rotate it in the API Locker.

3. Add the server

Add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json (this project only):

{
  "mcpServers": {
    "datafeeds": {
      "url": "https://mcp.datafeeds.rolling-insights.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:RSC_TOKEN}"
      }
    }
  }
}

If the file already exists, merge the datafeeds entry into the existing mcpServers object rather than replacing the file. The /mcp path is required — the bare hostname will not work. Note the env: prefix — it is Cursor's own syntax, and it is required. A reference without the prefix is not expanded: Cursor would send the placeholder text itself as your token and fail with an unhelpful 401.

4. Verify

Reload Cursor and check that datafeeds shows as enabled under Settings → MCP. That confirms the config parses, not that the token works — the server only validates it on a real call. So ask for live data in a chat:

Using the DataFeeds tools, what NBA games are on today?

A working connection returns real games. If it doesn't, troubleshooting below separates URL problems from token problems.

5. Enable the skill

The server above gives Cursor live data. The Sports AI Skill also teaches it the API's conventions — sport codes, season semantics, which endpoints exist per sport — so the code it writes against the REST API is right the first time. One command enables it:

npx skills add Rolling-Insights/sports-datafeeds-by-rolling-insights-skill -a cursor -y

-a scopes the skill to Cursor, and -y auto-confirms; the CLI prints its security assessment either way. The command needs Node.js 22.20.0 or newer — switch with nvm use 22 if npx reports EBADENGINE. It touches no MCP config and never involves your token.

Troubleshooting

# Confirm the variable is set — without printing its value.
[ -n "$RSC_TOKEN" ] && echo "RSC_TOKEN is set" || echo "RSC_TOKEN is NOT set"

curl -sS https://mcp.datafeeds.rolling-insights.com/healthz
# {"status":"ok"}