Connect polyscrape to your AI assistant.

Claude in the browser uses the same URL and signs in with polyscrape. Custom connectors are available on Claude Free (one custom connector), Pro, Max, Team and Enterprise. (Using the desktop app? See the Claude Desktop tab; connectors sync across both.)

1. 1
   In claude.ai, open Settings → Connectors.
2. 2
   Click Add custom connector.
3. 3
   Name it polyscrape, paste the server URL, and click Add:

   Server URL Copy

   https://polyscrape.com/mcp

4. 4
   Click Connect and sign in with polyscrape when prompted.
5. 5
   In any chat, open the tools menu (the under the message box), enable polyscrape, and ask away.

OAuth means there's no key to paste or leak — calls bill to your account, and you can disconnect any time from Claude.

Claude Desktop uses the same custom connectors as Claude.ai, and they sync across your Claude apps. Add it once and sign in with polyscrape — no config file, no key to paste.

1. 1
   Open Settings → Connectors in Claude Desktop (or add it on claude.ai — connectors sync to the desktop app).
2. 2
   Click Add custom connector.
3. 3
   Name it polyscrape, paste the server URL, and click Add:

   Server URL Copy

   https://polyscrape.com/mcp

4. 4
   Click Connect and sign in with polyscrape. The polyscrape tools appear under the tools menu — restart Claude if they don't show right away.

Advanced: some Claude Desktop builds also accept a local claude_desktop_config.json entry (type: http, url, and an Authorization: Bearer header). Use the connector flow above unless you know your build supports local remote-HTTP entries.

1. 1
   Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (this project). Cursor uses mcpServers with url + headers.

   ~/.cursor/mcp.json Copy

   {
     "mcpServers": {
       "polyscrape": {
         "url": "https://polyscrape.com/mcp",
         "headers": { "Authorization": "Bearer YOUR_API_KEY" }
       }
     }
   }

2. 2
   Enable polyscrape under Settings → MCP, then ask Cursor to call a tool.

Don't commit a real key in a project-level .cursor/mcp.json; prefer the global file or an environment variable.

1. 1
   VS Code uses its own shape, a servers map with "type": "http", plus an inputs prompt so the key isn't stored in the file. Add to .vscode/mcp.json (workspace) or your user mcp.json:

   .vscode/mcp.json Copy

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

2. 2
   VS Code prompts for your key the first time the server starts and stores it securely — paste your polyscrape API key when asked.

1. 1
   Windsurf (Cascade) uses serverUrl, not url, for remote servers. Add to ~/.codeium/windsurf/mcp_config.json:

   ~/.codeium/windsurf/mcp_config.json Copy

   {
     "mcpServers": {
       "polyscrape": {
         "serverUrl": "https://polyscrape.com/mcp",
         "headers": { "Authorization": "Bearer YOUR_API_KEY" }
       }
     }
   }

2. 2
   Fully quit and reopen Windsurf; closing the editor window alone won't reload MCP servers.

1. 1
   In Cline, open MCP Servers → Remote Servers → Edit Configuration (cline_mcp_settings.json) and add:

   cline_mcp_settings.json Copy

   {
     "mcpServers": {
       "polyscrape": {
         "type": "streamableHttp",
         "url": "https://polyscrape.com/mcp",
         "headers": { "Authorization": "Bearer YOUR_API_KEY" }
       }
     }
   }

2. 2
   Save — Cline reloads the server automatically.

Keep "type": "streamableHttp" — without it, Cline can fall back to legacy SSE, which polyscrape doesn't serve.