Claude & MCP

Connect claude.ai (web) or Claude Desktop to the hosted MCP. Connectors OAuth needs no API key. Market tools: spot, forward, vol, carry, whoami.

Copy for your LLM

Paste this into a setup chat only to wire the connector. Keep the setup short; do not invent Desktop config for web users.

You are a setup coach for the ZeroVaR R&D API MCP. Speak directly to the user in second person (“you”). Do not call them a colleague or talk about them in the third person.

Goal: Help you connect Claude or Cursor to https://staging.api.zerovar.com/mcp so tools return live market data without web search.

Facts:
- Portal: https://rd.deaglo.com
- Claude guide: https://rd.deaglo.com/claude
- MCP URL: https://staging.api.zerovar.com/mcp
- Preferred on claude.ai (web): no API key. In a chat, click + → Connectors → Add connector → Add custom connector. Name: ZeroVaR staging. URL: https://staging.api.zerovar.com/mcp. Leave OAuth Client ID and Client Secret blank. Add → Sign into ZeroVaR / Approve → enable the ZeroVaR staging toggle in Connectors.
- Same Connectors connector also works on Claude Desktop (Settings → Connectors). Still no API key for that path.
- PAT / mcp-remote: Claude Desktop ONLY. Not for claude.ai. Only if Connectors OAuth is unavailable.
- Cursor: mcp.json with "url": "https://staging.api.zerovar.com/mcp", then mcp_auth if prompted.
- Never paste a zvrd_… key into Slack or chat. Rotate if it was exposed.
- Rates are indicative, not executable quotes.
- Auth levels: spot/whoami/currencies/carry need CLIENT_VIEW+; history/forward/vol need PROVIDER+ (PREMIUM_MEMBER is enough). If whoami shows CLIENT_VIEW, do NOT say the platform has no forwards; say the account needs PROVIDER+ for those tools.
- market_forward: on defaults to today. Staging may return VALIDATION_FAILED “No forward rates available” until that day’s curve is published. Retry with on= prior calendar day (ISO date).
- Host tool/usage limits (claude.ai, Claude Desktop, Cursor, etc.) are the LLM host’s, not ZeroVaR’s. Do not blame the ZeroVaR API when a large multi-tool prompt stops mid-report. Keep smoke prompts small; continue big work in a new chat. See portal /claude#limits.

Rules:
- One step at a time; wait for confirmation.
- For claude.ai: never mention claude_desktop_config.json, mcp-remote, --env-file, or minting a key unless they ask for Sheets/Excel/Desktop PAT.
- Name MCP tools explicitly; do not invite web search as a fallback.

Procedure (say this to the user):
1. Ask: claude.ai (web), Claude Desktop, or Cursor?
2. If claude.ai: walk the + → Connectors → Add custom connector steps with Name and URL only (OAuth fields blank). Then ZeroVaR sign-in. Enable the connector toggle. No API key.
3. If Claude Desktop Connectors: same Name/URL path via Settings → Connectors. If they already have a local rd-api-mcp.mjs entry, remove it after Connectors works.
4. In this setup chat only: call whoami first. Report kind and level_name. Then one market call: market_spot or excel_spot for USD/SEK MID. Stop. Do not run a multi-pair audit here.
5. Tell them to go back to the chat where they already work (goals, clients, pairs) and enable the ZeroVaR staging connector there. Real FX work uses their known pairs — not a blank coach chat.
6. If they need forward/vol and whoami is CLIENT_VIEW: explain PROVIDER+ is required; do not conclude forwards are missing from the product.
7. If market_forward fails with no forward rates: retry with on= yesterday (ISO).

Done when: whoami returns a level, one spot tool returns a rate with as_of / source euthyphro (not Yahoo/Investing.com), and they know to continue in their existing work chat.

Use a new chat only to connect. Then go back to the chat where you already work and enable the connector there.

MCP URL

https://staging.api.zerovar.com/mcp

Hosted tools include whoami, excel_spot, market_spot, market_forward, market_volatility, market_spot_history, market_currencies, analytics_carry, and more. Which tools you see depends on your staging account access.

This page is the FX market MCP. Advisory project connections (for example QuickRisk swap valuation) are separate and listed under Projects.

1. claude.ai (web): add the connector

No API key required. In a chat on claude.ai:

Click + (bottom left of the composer).
Connectors → Add connector → Add custom connector.
Fill only:
- Name: ZeroVaR staging
- URL: https://staging.api.zerovar.com/mcp
- OAuth Client ID / Secret: leave blank
Click Add, then Sign into ZeroVaR and approve.
In the Connectors panel, turn the ZeroVaR staging toggle on for this chat.

The connector is account-level. Once added, you can enable it from any chat via + → Connectors. Claude reaches the MCP URL from Anthropic’s cloud.

2. First smoke (keep it tiny)

Run this once in the setup chat, then continue FX work in the chat that already knows your pairs and goals (enable the connector there). See usage limits if a long prompt stops mid-task.

Using only ZeroVaR staging MCP tools (do not web search), call whoami, then market_spot for USD/SEK MID. Report kind, level_name, rate, and as_of.

If some market tools are missing after whoami, that is usually staging account access, not a missing product. Ask your ZeroVaR contact for broader access.

Usage limits (Claude and other hosts)

When you use ZeroVaR from an LLM, two different systems are involved. Only one of them is ours.

Claude (claude.ai / Desktop) enforces its own usage and tool budgets under your Anthropic plan. A large multi-tool prompt can stop mid-task even when ZeroVaR is healthy. Prefer short prompts, a new chat for long reports, and only the connectors you need for that chat.
Other LLM hosts (for example Cursor) have their own usage caps. Treat those the same way: they are the host’s limits, not ZeroVaR API limits.
ZeroVaR controls which market tools your staging account can use. If a tool is unavailable, ask your ZeroVaR contact for broader staging access. That is account access, not a missing product.
Market data freshness: some series may not be available for “today” yet. Try a recent prior date.
Secrets: do not paste API keys into Claude, Slack, or other chats.

3. Optional follow-up prompts

Prefer the chat that already knows your work. Enable the connector there. Split large audits across chats only if you hit your host’s tool budget.

Using only ZeroVaR staging MCP tools (do not web search), call market_volatility for USD/SEK. If market_forward is available at my level, call it for USD/SEK with horizon_weeks=13; if that fails with no forward rates for today, retry with on set to yesterday (ISO date). Report annualised_vol and any forward mid with as_of.

If market_forward is listed for my level, get USD/SEK spot and 13w forward via MCP (pass on= prior day if today has no forward curve), then analytics_carry for that spot, forward, and tenor_weeks=13. If forward tools are unavailable for my account, say so from whoami and stop. No web search.

4. Claude Desktop (Connectors)

Same Name / URL as web: Settings → Connectors → Add custom connector. No API key. If an old local rd-api-mcp.mjs entry is still in claude_desktop_config.json, remove it so only the hosted connector remains.

5. API keys (only for Sheets, Excel, or Desktop PAT)

Claude Connectors do not need a personal key. Create one only for Google Sheets, Excel VBA, or Desktop mcp-remote.

Get API key Sheets Excel

Never paste a zvrd_… secret into Slack or chat. If one was shared, rotate it on the keys page.

6. Claude Desktop only: PAT via `mcp-remote`

Not available on claude.ai. Prefer Connectors. If you need a static zvrd_… key on Desktop:

{
  "mcpServers": {
    "zerovar-rd-api-staging": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://staging.api.zerovar.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer zvrd_…"
      }
    }
  }
}

macOS config path: ~/Library/Application Support/Claude/claude_desktop_config.json

MCP URL must be the first positional argument to mcp-remote.
Do not pass --env-file (causes Invalid URL).
${AUTH_HEADER} expands from the "env" block only.
Fully quit and reopen Claude Desktop after saving.

7. Cursor

In ~/.cursor/mcp.json (or project MCP settings):

{
  "mcpServers": {
    "zerovar-rd-api-staging": {
      "url": "https://staging.api.zerovar.com/mcp"
    }
  }
}

Authenticate when prompted (mcp_auth).

Troubleshooting

Instructions feel heavy: on claude.ai you only need Name + URL in Add custom connector, then Sign into ZeroVaR. No config file, no API key.
Claude tool limit after one prompt: that is Anthropic’s tool-use budget, not the ZeroVaR API. See usage limits. Use the tiny smoke prompt, then continue in a new chat.
Some tools missing: check whoami, then ask your ZeroVaR contact for broader staging access. Do not treat this as a missing product.
No forward rates for today: pass on as a prior calendar day. Not an auth issue.
“Server disconnected” (Desktop PAT path): open View Logs first. Often --env-file or wrong arg order.
404 storm / “API is down”: remove local rd-api-mcp.mjs; use only the hosted Connectors URL.
Keys page “Could not register sign-in client (403)”: not needed for Claude Connectors. For Sheets/Excel keys, hard-refresh the CloudFront portal, try incognito or another device, or clear site data for this origin. Escalate platform DCR 403 to Rhys if it persists.