API Keys

Name	Key	Scopes	Rate Limit	Last Used	Created	Expires	Actions

Use your API key to connect WaiConnect to any MCP-compatible tool. Select your client below for setup instructions.

Claude Code has native streamable-http support. Run this single command:

Terminal

claude mcp add --transport http \
  --header "Authorization: Bearer YOUR_API_KEY" \
  waiconnect https://waiconnect.io/mcp/

Or add to your project's .mcp.json for team sharing:

.mcp.json

{
  "mcpServers": {
    "waiconnect": {
      "type": "http",
      "url": "https://waiconnect.io/mcp/",
      "headers": {
        "Authorization": "Bearer ${WAICONNECT_API_KEY}"
      }
    }
  }
}

Set WAICONNECT_API_KEY in your environment, or use the CLI command above with the key directly. Verify with claude mcp list.

Add to .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global):

.cursor/mcp.json

{
  "mcpServers": {
    "waiconnect": {
      "url": "https://waiconnect.io/mcp/",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Cursor detects config changes automatically. You can also add via Settings → Tools & MCP → New MCP Server.

Add to .vscode/mcp.json in your project (requires VS Code 1.99+ with GitHub Copilot):

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "waiconnect-key",
      "description": "WaiConnect API Key",
      "password": true
    }
  ],
  "servers": {
    "waiconnect": {
      "type": "http",
      "url": "https://waiconnect.io/mcp/",
      "headers": {
        "Authorization": "Bearer ${input:waiconnect-key}"
      }
    }
  }
}

VS Code will securely prompt for your API key on first use. Note: VS Code uses "servers" instead of "mcpServers".

Edit ~/.codeium/windsurf/mcp_config.json (or open via Settings → Cascade → MCP Servers):

mcp_config.json

{
  "mcpServers": {
    "waiconnect": {
      "serverUrl": "https://waiconnect.io/mcp/",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Windsurf uses "serverUrl" for remote servers. Supports env vars with ${env:WAICONNECT_API_KEY} syntax.

Claude Desktop now supports native remote connectors in Settings → Connectors for authless or OAuth-capable servers. WaiConnect currently uses static Bearer API keys, so use the mcp-remote bridge below:

claude_desktop_config.json

{
  "mcpServers": {
    "waiconnect": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://waiconnect.io/mcp/",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Config file location:

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

Windows: %APPDATA%\Claude\claude_desktop_config.json

Requires Node.js 18+ installed. Restart Claude Desktop after editing the config.

If you're using Anthropic's Messages API MCP connector, pass WaiConnect as a remote server and send your WaiConnect API key as authorization_token:

Messages API payload fragment

{
  "mcp_servers": [
    {
      "type": "url",
      "url": "https://waiconnect.io/mcp/",
      "name": "waiconnect",
      "authorization_token": "YOUR_API_KEY"
    }
  ],
  "tools": [
    {
      "type": "mcp_toolset",
      "mcp_server_name": "waiconnect"
    }
  ]
}

Use Anthropic's current MCP connector beta header (anthropic-beta: mcp-client-2025-11-20). This is the supported Anthropic path for static Bearer-style WaiConnect API keys.

Paste this into Settings → Connectors → Add custom connector in Claude.ai:

Claude.ai connector

Name: WaiConnect
Remote MCP server URL:
https://waiconnect.io/mcp/?key=YOUR_API_KEY

Create or rotate a key to generate a paste-ready URL with the real key embedded
In Claude.ai, add the connector using the copied block above
In a new chat, use the + button → Connectors to enable WaiConnect

Security note: The connector URL itself is secret because it contains your API key. Treat it the same way you would treat the raw key.

Authentication Required

API Keys

Connect Your Tools