MCP quickstart

Connect any MCP-compatible AI client to Scrapewise. After this, Claude can search Google and Amazon, find local businesses, fetch a web page and read the rows saved in your account, by asking in natural language. With the setup tools switched on in the address (Step 2) it also builds and runs scrapers.

Step 1 — Mint an API key with an MCP-capable scope

In the portal: Settings → API Keys → Create new key.

For the Scope field, pick:

• LLM_READ — read-only access. The agent can list your groups and read saved rows and job results. It cannot call a paid tool, and it cannot create/run/delete anything. Recommended for the first time you connect Claude.
• LLM_FULL — read + write. The agent can also call the paid tools (searches, page fetches, long jobs) and, with the setup tools on, create scrapers, run them, delete data. Building a scraper needs this scope.

Avoid USER for MCP — USER-scope keys are explicitly rejected by the MCP gateway (returns 403 scope_rejected).

Copy the key. It looks like sw_live_abc1234.<long-secret>.

Step 2 — Connect your MCP client

The MCP gateway is at https://mcp.scrapewise.ai/mcp. A Full key (LLM_FULL) lists every tool. A Read key (LLM_READ) lists the read tools.

Three clients walked through below.

Claude Desktop

Open Claude Desktop → Settings → Developer → Edit Config. Add this to the mcpServers block (creating the block if it’s not there):

{
  "mcpServers": {
    "scrapewise": {
      "url": "https://mcp.scrapewise.ai/mcp",
      "headers": {
        "Authorization": "Bearer sw_live_abc1234.your-secret-here"
      }
    }
  }
}

Replace sw_live_abc1234.your-secret-here with the key you minted in Step 1.

Quit Claude Desktop (Cmd-Q / fully close — not just the window) and reopen. In the conversation input, type / and you should see Scrapewise tools available.

Claude Code

One command:

claude mcp add scrapewise --transport http https://mcp.scrapewise.ai/mcp \
  --header 'Authorization: Bearer sw_live_abc1234.your-secret-here'

Verify with claude mcp list — scrapewise should appear with status ✓.

claude.ai (web)

Sign in to claude.ai  → click your initials (top-right) → Settings → Connectors → Add Custom Connector.

Fill in:

Save. In a new conversation, the Scrapewise tools appear in the tool list.

Step 3 — Try it

In any of the three clients, with either address, ask:

“List my Scrapewise groups”

or, with an LLM_FULL key (the price quote costs nothing):

“Find 5 dentists in Tallinn with phone number and website. Tell me the price first.”

With an LLM_FULL key you can also ask:

“Scrape https://example.com  and tell me what fields are visible”

Claude picks the right tool, calls it, and shows you the result. On a new account the list of groups is empty; an empty answer still means the connection works.

What tools are exposed?

Outcome tools:

A Full key lists the setup tools too. Every REST endpoint under the MCP-tag in the OpenAPI spec  is surfaced as an MCP tool. The setup tools cover:

For the full tool catalog with input/output schemas, see MCP tools.

What it costs

Nothing to subscribe to. Scrapewise is prepaid pay-as-you-go: you top the wallet up, and the tools that fetch a page are charged per page delivered — from €0.00015 for a plain page (€0.15 per 1,000). Listing, reading and exporting cost nothing. The short-list tools state their price in credits (1 credit is €0.00015), and a call with quote_only: true returns the price and your wallet balance without spending anything. A new account starts with 5 free requests. Connecting, listing your groups and asking for a price quote cost nothing at all.

If the wallet runs out, a fetching tool comes back as a tool error reading HTTP 402 with the code WALLET_INSUFFICIENT_BALANCE. That is a refusal, not a glitch — top up and repeat the call. Full price list and top-up flow: Wallet & billing.

Permissions

The agent inherits your key’s scope. With an LLM_READ key, it can only call read-only tools; with LLM_FULL it can call the paid tools and destructive tools too. There’s no separate consent prompt for each tool call — if you don’t want Claude to delete scrapers, give it an LLM_READ key.

For more on scope semantics, see Scopes.

Troubleshooting

• Only a few tools show up, and none that creates or runs a scraper — the key is LLM_READ. Create an LLM_FULL key.
• 403 scope_rejected from any tool call — your key’s scope can’t call this tool. Mint a higher-scope key.
• 401 Unauthorized — bad Authorization header. Check the Bearer prefix.
• Tools don’t show up in Claude Desktop — fully quit and reopen (Cmd-Q, not just close window). Verify the config JSON is valid.
• 429 Too Many Requests — you’re rate-limited. Wait the Retry-After seconds.
• HTTP 402 with WALLET_INSUFFICIENT_BALANCE — the wallet is out of balance and out of free requests. Top up, then repeat the call; retrying without topping up returns the same 402.
• Tool result contains prompt-injection content — Scrapewise marks scraped content with type: "scraped" in the response envelope. See Prompt injection for the agent-side defense.

What’s next

• Full MCP gateway documentation → MCP overview
• Prompt-injection defense → Prompt injection
• REST surface (for non-LLM integrations) → REST quickstart