Skip to main content
The endpoint is the same everywhere:
Authenticate with your RAIL API key. The server accepts it either as a bearer token (Authorization: Bearer rail_...) or as an X-API-Key: rail_... header — use whichever your client offers. Never commit the key; use an environment variable or your client’s secret store.

Claude Code

Claude (claude.ai / Desktop)

Settings → Connectors → Add custom connector → URL https://mcp.responsibleailabs.ai/mcp, then paste your rail_ key when prompted.

Cursor and Windsurf

.cursor/mcp.json:

VS Code / GitHub Copilot

.vscode/mcp.json — same shape, with "type": "http" and an input prompt for the key so it is never committed.

Vercel v0

Settings → Integrations → Add Custom MCP Connection:
  • Name: RAIL
  • URL: https://mcp.responsibleailabs.ai/mcp
  • Authentication: choose Bearer and paste your rail_ key (v0 sends it as Authorization: Bearer). Or choose Headers and add X-API-Key = rail_YOUR_KEY.
Then Add — v0 connects and lists the rail_ tools.

OpenAI Responses API

LangGraph / LangChain

Replit Agent

Project → Integrations → “MCP Servers for Replit Agent” → Add MCP server → URL https://mcp.responsibleailabs.ai/mcp plus an Authorization header (store the key in Replit Secrets) → Test & Save. On Enterprise plans an admin must enable MCP first.
For apps built on Replit (not the Agent), call the Python or JavaScript SDK directly inside the app. MCP is for agent runtimes; the SDK is for application code.