Connect claude.ai (web)

Use Scrapewise from claude.ai in your browser. ~2 minutes via Custom Connectors.

Prerequisites

A claude.ai account
A Scrapewise API key with scope LLM_READ or LLM_FULL. See Scopes.

Walkthrough

1 — Open Custom Connectors

Sign in to claude.ai
Click your initials (top-right) → Settings
In the left sidebar, find Connectors
Click Add Custom Connector (top-right of the Connectors panel)

2 — Fill in the connector

A dialog opens. Fill it in:

Field	Value
Name	`Scrapewise` (or anything you’ll recognize)
MCP Server URL	`https://mcp.scrapewise.ai/mcp`
Authentication	Select Custom header (NOT OAuth)
Header name	`Authorization`
Header value	`Bearer sw_live_abc1234.your-secret-here` (replace with your key, include `Bearer` with space)

Click Save / Add.

A Full key (LLM_FULL) lists every tool. A Read key (LLM_READ) lists the read tools.

3 — Verify

claude.ai pings the gateway, discovers tools, and lists them on the connector page. You should see the connector marked as connected, with a number of tools. The number depends on the key’s scope.

If you see “Failed to connect” or “0 tools,” see Troubleshooting below.

4 — Use it in a conversation

Start a new conversation. Above the input box you’ll see a tools icon (a wrench or plug — the exact symbol depends on claude.ai version). Click it and verify Scrapewise tools are toggled on for this conversation.

Try:

List my Scrapewise groups

Claude calls scrapewise_get_scraper_group_list and shows the result. This tool is on both lists and costs nothing. An empty list on a new account still means the connection works.

With an LLM_FULL key you can also try:

Preview a scrape of https://example.com — look for title and main heading

Claude calls scrapewise_preview_scraper_from_url and shows the result.

Update the key

To rotate the key:

Settings → Connectors
Click your Scrapewise connector
Edit the Header value with the new bearer string
Save

Disable temporarily

In a conversation, click the tools icon → toggle Scrapewise off for this conversation. The connector remains registered but isn’t exposed to that chat.

Remove

Settings → Connectors → click your Scrapewise connector → Delete connector at the bottom of the page.

Troubleshooting

”Failed to connect” when saving

401: bad bearer. Re-check the header value — must be exactly Bearer (with space) followed by the full sw_live_<prefix>.<secret>.
403: key scope is USER. The MCP gateway needs LLM_READ or higher. Mint a new key.
Network error: claude.ai couldn’t reach mcp.scrapewise.ai. Rare — check from a different network if persistent.

Only a few tools, and none that creates or runs a scraper

Tools that create or run are missing: the key is LLM_READ. Create an LLM_FULL key.

Connector saves but shows “0 tools”

Click into the connector → look at the Last error field. Most often this is 403 scope_rejected (which means auth worked but the key’s scope is wrong).

Tool calls inside a conversation return errors

Open the tool-call expansion in the chat — the error envelope from Scrapewise has a correlationId you can paste into a support ticket.
For 429, wait the Retry-After seconds and ask again.
For 429 cost_exceeded, you’ve hit the hourly cost budget — wait until the next hour.

What’s next

Tool catalog → Tools
Prompt-injection contract → Prompt injection
Connect Claude Desktop → Claude Desktop
Connect Claude Code (CLI) → Claude Code
Use Scrapewise in n8n → Connect n8n