Scrappey MCP Server

Official Node.js client for the Scrappey web scraping API. Render and retrieve web pages, automate browser actions, manage persistent sessions, and

Local serverstdioPython

What is the Scrappey MCP server?

Scrappey MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Official Node.js client for the Scrappey web scraping API. Render and retrieve web pages, automate browser actions, manage persistent sessions, and route through residential proxies for reliable collection of publicly available data. Ships.

What you get

  • Browser automation — Full browser actions (click, type, scroll, execute JS)
  • Session management — Persistent sessions with cookie and state management
  • All HTTP methods — GET, POST, PUT, DELETE, PATCH
  • Proxy support — Built-in residential proxies with country selection
  • Screenshots & video — Capture screenshots and record browser sessions
  • TypeScript support — Full TypeScript declarations included

What the assistant can call

Once Scrappey is connected, these are the calls the assistant has available:

  • Configuration — // Set defaults axios.defaults.apiKey = 'YOUR_API_KEY'; axios.defaults.premiumProxy = true; axios.defaults.timeout = 60000;
  • Constructor — The Constructor tool exposed by this server

Configuration and credentials

You will need one environment variable: YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at scrappey-wrapper on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Scrappey's toolset — Configuration, Constructor — is a fair guide to whether it matches your workflow. It is maintained by dormic97; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Scrappey's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the scrappey mcp server does with a few real requests.

Available tools

ToolWhat it does
Configuration// Set defaults axios.defaults.apiKey = 'YOUR_API_KEY'; axios.defaults.premiumProxy = true; axios.defaults.timeout = 60000;
ConstructorThe Constructor tool exposed by this server.

How to install the Scrappey MCP server

{
  "mcpServers": {
    "scrappey": {
      "command": "npx",
      "args": ["-y", "scrappey-wrapper"],
      "env": {
        "YOUR_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
YOUR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Scrappey to Configuration.
  • Use Scrappey to Constructor.

Frequently asked questions

It connects Scrappey to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Configuration, Constructor) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Scrappey directly.