Claude Code Plugin

The SuperScraper Claude Code plugin registers the SuperScraper MCP server and adds three slash commands in one step. After installing, Claude Code can scrape, extract, and pull lead lists without any additional configuration.

What the plugin adds

Slash commands

The plugin directory and its command files still carry the project's original leadsnap prefix in source (plugins/leadsnap/commands/), so these are the literal names Claude Code will show:

Command	What it does
`/leadsnap-pull`	Pull a structured lead list from any source in the connector registry
`/leadsnap-scrape`	Scrape / extract / crawl one or many URLs
`/leadsnap-connectors`	List all registered connectors with pricing and region info

MCP tools (registered automatically)

Tools from the SuperScraper MCP server become available directly in the conversation.

See the MCP Server guide for the full tool reference.

Installation

Prerequisites

Claude Code (opens in a new tab) installed
Node.js 18+ (for npx tsx)
A SuperScraper API key, get one free at app.superscraper.dev (opens in a new tab)

Step 1, Set your API key

Add the key to your shell profile or a .env file in your project:

export SUPERSCRAPER_API_KEY=ss_live_xxxxxxxxxxxxxxxxxxxx

Step 2, Register the MCP server

Merge the following into your project's .mcp.json (create it in the repo root if it does not exist):

{
  "mcpServers": {
    "superscraper": {
      "command": "npx",
      "args": ["--yes", "tsx", "/absolute/path/to/superscraper/packages/mcp/src/index.ts"],
      "env": {
        "SUPERSCRAPER_API_URL": "https://api.superscraper.dev",
        "SUPERSCRAPER_API_KEY": "ss_live_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

If you are inside the SuperScraper repo itself, use the relative path packages/mcp/src/index.ts. Otherwise, use the absolute path.

Step 3, Add the slash commands

Copy the commands/ directory from the plugin into your .claude/ folder:

# From the superscraper repo root
cp -r plugins/leadsnap/commands .claude/commands/leadsnap

Or, if you cloned SuperScraper separately:

cp -r /path/to/superscraper/plugins/leadsnap/commands ~/.claude/commands/leadsnap

Step 4, Reload Claude Code

Restart Claude Code (or run /reload). The slash commands appear in the command palette and the MCP tools appear in the tools panel.

Quick start

After installing, try these in a Claude Code conversation:

/leadsnap-pull HVAC contractors in Denver CO maxResults=30

/leadsnap-scrape https://www.servicetitan.com/pricing --extract "plan name, price, features"

/leadsnap-connectors

Or use natural language, Claude will call the right tools automatically:

"Find 50 roofing contractors in Austin with phone numbers, check which ones use ServiceTitan, and make a CSV."

Hosted MCP is not available

Do not configure a hosted MCP URL. Call the REST API (POST /v1/scrape and the rest of /v1) with a Bearer key. Local stdio MCP is developer-only.

Troubleshooting

The MCP tools are not showing up

Make sure .mcp.json is in the repo root (or your home dir for global config).
Confirm SUPERSCRAPER_API_KEY is set in the env block inside .mcp.json.
Check that npx tsx can run (node --version should be 18+).

list_tools returns no connectors

The connector registry is populated at server start. If the server started before the connectors package was installed, restart Claude Code.

pull_mercado_libre returns an error about proxy

Mercado Libre requires a residential IP in Brazil or Mexico. Set OXYLABS_USERNAME/OXYLABS_PASSWORD or BRIGHTDATA_* env vars and restart.

Slash commands not appearing

Make sure the .md files are in .claude/commands/ (or ~/.claude/commands/ for global) and that the filenames match the command names without the leading slash.

Hosted MCP URL shape

Hosted MCP is not available. Do not paste a hosted MCP URL into client config.

CLI LangChain