Overview

Rapid MCP supports authentication via HTTP headers. You can:

• Set headers at the MCP server level (recommended). These are automatically passed to each tool call.
• Reference those headers inside a tool's Headers section using template variables like {{api-key}}.

OAuth is planned and coming soon.

Video Walkthrough

1) MCP server-level headers (API key)

Add an API key at the server level so it is forwarded to every tool call:

{
  "mcpServers": {
    "RapidMCP": {
      "url": "https://rapid-mcp.com/mcp/<serverId>/stream",
      "headers": {
        "Authorization": "Bearer XXXXX",
        "api-key": "example-api-key"
      }
    }
  }
}

Notes:

• Keys in headers are exposed to tools as template variables. For example, api-key → {{api-key}}.
• Keep header keys lowercase and without spaces for clean templating.

2) Tool-level headers using {{api-key}}

Inside a tool, add headers that reference the server-level API key:

Authorization: Bearer {{api-key}}
x-api-key: {{api-key}}

Add these in the tool editor under "Headers".

Tip: You can hardcode tokens per tool, but managing them at the server level makes rotation and reuse across tools easier.

3) Code example

Reference these variables in the tool custom code via the string template examples below:

async function code(inputs: ToolArguments) {
  const apiKey = "{{api-key}}" // <-- here will get interpolated with the server-level header value
  const subdomain = "{{subdomain}}" // <-- here will get interpolated with the server-level header value

  const response = await fetch(`https://${subdomain}.example-api.com/v1/${inputs.projectId}/stats`, {
    headers: {
      Authorization: `Bearer ${apiKey}`
    }
  })

  return response.json()
}

4) OAuth (coming soon)

We are adding first-class OAuth support. Planned flow:

• Configure OAuth client credentials at the server level
• Complete authorization once to securely store tokens
• Tokens automatically injected as request headers for tool calls

This section will be updated when available.