AI assistants · Any MCP client

Other clients

Connect any client that speaks MCP over HTTP and can send a header.

MCP server
https://mcp.rolodexy.ai

What you need

  • An MCP client that supports Streamable HTTP and custom headers, or Node.js for the bridge.
  • A Rolodexy API key.

Set it up

  1. Create an API key

    In Rolodexy, open Settings → API keys and create a key for this assistant. Copy it; it is shown once.

  2. Point the client at the server

    Use the Streamable HTTP transport with this address, and send the key in the X-API-Key header or as Authorization: Bearer.

    Server
    https://mcp.rolodexy.ai
  3. Clients that only run local servers

    If the client can only start a local command, run mcp-remote as a bridge.

    Command
    npx -y mcp-remote https://mcp.rolodexy.ai --header "X-API-Key:rdx_your_key"
  4. Test it by hand

    The server answers JSON-RPC over POST. This lists the tools:

    Terminal
    curl -X POST https://mcp.rolodexy.ai \
      -H "X-API-Key: rdx_your_key" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

Try a first prompt

“Using Rolodexy, find 10 heads of sales at software companies in Germany with 51 to 200 people. Show me the list before revealing anyone.”

Searching is free. Revealing a contact spends credits, so asking to see the list first keeps you in control. See Tools and pricing.

Troubleshooting

405 Method Not Allowed
The server takes POST only and does not open a server-sent event stream. Clients that require one should use the mcp-remote bridge.
Protocol version
Supported versions are 2025-06-18, 2025-03-26 and 2024-11-05.
401 unauthorized
The key is missing, mistyped or revoked. Check there are no spaces or quotes around it, or create a new one.
402 insufficient_credits
The workspace is out of credits. Searching still works; top up on the Billing page to reveal more.