Scrapewise MCP server

ScrapeWise MCP Server

Scrape, clean and match product and price data from any website — from inside your AI agent.

ScrapeWise runs a hosted Model Context Protocol server. You point your MCP client at one URL and add your API key. Your agent can then read product and price data from any shop or from Amazon, find local businesses, search Google and Amazon, fetch web pages and read the rows saved in your account. Add ?toolsets=outcome,admin to the URL and it also builds and runs scrapers.

• Endpoint: https://mcp.scrapewise.ai/mcp
• Endpoint with the setup tools (to build scrapers): https://mcp.scrapewise.ai/mcp?toolsets=outcome,admin
• Transport: Streamable HTTP
• Registry name: ai.scrapewise/scrapewise (official MCP registry)
• Auth: Authorization: Bearer
• Docs: scrapewise.ai/mcp

This repository holds the connection manifest and the per-client config for that server. The server itself is hosted — there is nothing here to install or run.

Get an API key

Sign up at scrapewise.ai, then go to Settings → API Keys and create one. Pricing is pay-as-you-go.

Connect

Replace YOURSCRAPEWISEAPI_KEY in every snippet below.

These snippets connect to the short list of data tools. To build scrapers as well, use this address in the same place:

https://mcp.scrapewise.ai/mcp?toolsets=outcome,admin

An account that gets its first MCP key now sees only the short list at the bare address. Accounts that still hold an older MCP key keep every tool. The choice is read when the session starts, so reconnect after changing it. Spell it toolsets: a misspelt switch is ignored without an error.

Claude Code

claude mcp add scrapewise --transport http https://mcp.scrapewise.ai/mcp \
  --header 'Authorization: Bearer YOUR_SCRAPEWISE_API_KEY'

With the setup tools. The single quotes are needed: in zsh an unquoted ? breaks the command.

claude mcp add scrapewise --transport http 'https://mcp.scrapewise.ai/mcp?toolsets=outcome,admin' \
  --header 'Authorization: Bearer YOUR_SCRAPEWISE_API_KEY'

Claude Desktop

claudedesktopconfig.json:

{
  "mcpServers": {
    "scrapewise": {
      "url": "https://mcp.scrapewise.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SCRAPEWISE_API_KEY"
      }
    }
  }
}

Cursor

Same shape, in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "scrapewise": {
      "url": "https://mcp.scrapewise.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SCRAPEWISE_API_KEY"
      }
    }
  }
}

VS Code

VS Code is the odd one out: the map is servers, not mcpServers, and a remote server has to name its transport with "type": "http". Get either wrong and VS Code skips the entry without telling you.

Open the Command Palette → MCP: Open User Configuration, then:

{
  "servers": {
    "scrapewise": {
      "type": "http",
      "url": "https://mcp.scrapewise.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SCRAPEWISE_API_KEY"
      }
    }
  }
}

Anything else

Any client that speaks Streamable HTTP works. Give it the endpoint, the Authorization header, and the name scrapewise.

What your agent can do

Shortened. The full README is on GitHub.