Claude Code

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

Claude Code 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'

Then open a new terminal, or source the profile, so the variable is live in the session you start Claude Code from.

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 Claude Code 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 .mcp.json in your project root (or ~/.claude.json to make it available everywhere):

{
  "mcpServers": {
    "datafeeds": {
      "type": "http",
      "url": "https://mcp.datafeeds.rolling-insights.com/mcp",
      "headers": {
        "Authorization": "Bearer ${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. ${RSC_TOKEN} is Claude Code's own expansion syntax: it reads the variable at run time, so the token's value never touches the file.

A note on mcp add commands. Set the server up by editing the file, as above — not with a shell command like:

# Don't do this — the token ends up in the file in plaintext.
claude mcp add --transport http datafeeds https://mcp.datafeeds.rolling-insights.com/mcp \
  --header "Authorization: Bearer ${RSC_TOKEN}"

Your shell expands ${RSC_TOKEN} before Claude Code ever sees the argument, so what gets written to the config is your live token in clear text — exactly the outcome the environment-variable pattern exists to avoid.

4. Verify

Restart Claude Code, then run claude mcp list — datafeeds should report connected. That check proves the config parses, not that the token works: with RSC_TOKEN unset, Claude Code warns but still passes the literal placeholder through, and the failure only surfaces on a real call. So ask for live data:

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 Claude Code 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 claude-code -y

-a scopes the skill to Claude Code, 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"}