MCP Server

Claude Desktop does not support custom headers directly for remote MCP servers. Use mcp-remote as a bridge to handle authentication.

Add this to your Claude Desktop configuration file:

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

Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "whitepages": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.whitepages.com/mcp",
        "--header",
        "X-Api-Key: ${WHITEPAGES_API_KEY}"
      ],
      "env": {
        "WHITEPAGES_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

After saving, restart Claude Desktop for the changes to take effect.

Claude Code connects to remote HTTP servers with custom headers directly — no bridge needed. Add the MCP server using the CLI or edit your configuration file directly.

Using CLI:

claude mcp add --transport http whitepages https://api.whitepages.com/mcp \
  --header "X-Api-Key: YOUR_API_KEY_HERE" --scope user

Or edit ~/.claude.json (macOS/Linux) or %USERPROFILE%\.claude.json (Windows):

{
  "mcpServers": {
    "whitepages": {
      "type": "http",
      "url": "https://api.whitepages.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

After running claude mcp add, reconnect with /mcp in an open session. A full restart is only needed if you edited ~/.claude.json by hand.

Add the server with a single codex mcp add command. It uses mcp-remote as a stdio bridge to send the X-Api-Key header:

codex mcp add whitepages -- npx -y mcp-remote https://api.whitepages.com/mcp \
  --header "X-Api-Key: YOUR_API_KEY_HERE"

Or edit ~/.codex/config.toml directly to connect to the remote server natively, without the mcp-remote bridge:

[mcp_servers.whitepages]
url = "https://api.whitepages.com/mcp"
http_headers = { "X-Api-Key" = "YOUR_API_KEY_HERE" }

In the codex TUI, run /mcp to confirm the server is connected.

Gemini CLI connects to remote Streamable HTTP servers with custom headers. Add the server with the CLI or edit your settings.json directly.

Using CLI:

gemini mcp add whitepages https://api.whitepages.com/mcp \
  --transport http --header "X-Api-Key: YOUR_API_KEY_HERE"

Or edit ~/.gemini/settings.json:

{
  "mcpServers": {
    "whitepages": {
      "httpUrl": "https://api.whitepages.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Run /mcp inside Gemini CLI to confirm the server is connected.

Cursor supports remote HTTP servers with custom headers directly. Add this to your Cursor MCP settings file:

macOS/Linux: ~/.cursor/mcp.json

Windows: %USERPROFILE%\.cursor\mcp.json

{
  "mcpServers": {
    "whitepages": {
      "url": "https://api.whitepages.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Restart Cursor after updating the configuration.

Cline supports custom headers directly for remote MCP servers.

In VS Code with Cline extension:

1. Click the MCP Servers icon in the Cline panel
2. Select the Configure tab
3. Click "Edit MCP Settings" to open cline_mcp_settings.json
4. Add this configuration:

{
  "mcpServers": {
    "whitepages": {
      "url": "https://api.whitepages.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

OpenCode supports custom headers directly for remote MCP servers.

Add this to your opencode.json configuration:

{
  "mcp": {
    "whitepages": {
      "type": "remote",
      "url": "https://api.whitepages.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY_HERE"
      },
      "enabled": true
    }
  }
}

Zed currently focuses on stdio-based MCP servers. Use mcp-remote to connect to remote servers.

Add this to your Zed settings (~/.config/zed/settings.json or via Zed → Settings):

{
  "context_servers": {
    "whitepages": {
      "command": {
        "path": "npx",
        "args": [
          "mcp-remote",
          "https://api.whitepages.com/mcp",
          "--header",
          "X-Api-Key: YOUR_API_KEY_HERE"
        ]
      }
    }
  }
}

While Postman doesn't directly support MCP, you can test the underlying API:

1. Create a new request
2. Set method to POST
3. Set URL to https://api.whitepages.com/mcp
4. Add headers:
   • Content-Type: application/json
   • Accept: text/event-stream
   • X-Api-Key: YOUR_API_KEY_HERE
5. Set body (raw JSON):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2024-11-05",
    "capabilities": {},
    "clientInfo": {
      "name": "postman-test",
      "version": "1.0.0"
    }
  }
}

The MCP Inspector is the official tool for testing MCP servers:

1. Install and run:

npx @modelcontextprotocol/inspector https://api.whitepages.com/mcp

2. In the Inspector UI:

   • Transport Type: SSE
   • URL: https://api.whitepages.com/mcp
   • Click Authentication button
   • Add header: X-Api-Key = YOUR_API_KEY_HERE
   • Click Connect

3. Once connected, you can explore available tools and test them interactively.