Skip to main content

​
MCP Server

ScrapeBadger provides a hosted MCP (Model Context Protocol) server at mcp.scrapebadger.com that lets AI agents access all ScrapeBadger APIs through structured, typed tools.

​
What is MCP?

Model Context Protocol is an open standard by Anthropic for connecting AI models to external tools and data sources. Instead of writing code, your AI agent discovers and calls ScrapeBadger tools naturally during a conversation.

​
Key Features

344 Tools

Every ScrapeBadger API endpoint is available as a typed MCP tool with structured parameters, annotations, and output schemas.

Zero Setup

Hosted at mcp.scrapebadger.com — connect Claude with one click, or add one config snippet to any other AI tool.

10 Platforms

Works with Claude, Cursor, Windsurf, VS Code, Gemini, ChatGPT, OpenClaw, Cline, and more.

Same Pricing

No extra cost — MCP uses the same credit-based pricing as the REST API.

30 Products

Twitter/X, Instagram, Facebook, LinkedIn, Google, YouTube, TikTok, Reddit, Amazon, eBay, Walmart, Vinted, Depop, real estate, search engines, LLM answers, and general web scraping — all in one server.

Latest MCP Standard

Speaks the stateless 2026-07-28 protocol revision and every earlier one; OAuth 2.1 with PKCE, resource indicators, and Client ID Metadata Documents.

​
Available Tools

​
Google Tools

Google MCP tools are prefixed with google_ — highlights:

​
Quick Start

Using Claude? No API key needed:
1

Add the Connector

In claude.ai (or Claude Desktop), go to Settings > Connectors > Add custom connector and enter https://mcp.scrapebadger.com/mcp.
2

Sign In and Approve

Click Connect — you’ll be redirected to sign in with your ScrapeBadger account and approve access. That’s the whole setup.
3

Start Using Tools

Ask Claude to search tweets, scrape websites, or look up products — it discovers and calls the right tools automatically.
Using another AI tool? Sign up at scrapebadger.com, create an API key from the dashboard, and grab the config snippet from the integration guides.

​
Authentication

Two authentication modes are supported: Clients that support MCP OAuth (claude.ai, Claude Desktop, Claude Code, ChatGPT) can connect without any key handling: add the server URL, sign in with your ScrapeBadger account, and approve the consent screen. Access is tied to your account’s API key and can be revoked anytime by deactivating that key in the dashboard.

​
API key

​
Protocol & Standards

The server tracks the latest MCP specification (revision 2026-07-28):
  • Protocol versions — speaks the stateless 2026-07-28 revision (per-request versioning, server/discover) and serves every earlier revision (2025-11-25, 2025-06-18, …) from the same endpoint, so older clients keep working. Streamable HTTP transport only; the deprecated HTTP+SSE transport is not offered.
  • Tool metadata — all 344 tools carry a human-readable title, readOnlyHint/destructiveHint/openWorldHint annotations, and an output schema. Tool results are size-capped to stay within client limits, and the tool list is served with cache hints (ttlMs/cacheScope) for faster clients.
  • OAuth 2.1 — authorization code + PKCE (S256), refresh-token rotation, RFC 8414 authorization-server metadata, RFC 9728 protected-resource metadata, RFC 8707 resource indicators, RFC 9207 iss authorization responses, and Client ID Metadata Documents (HTTPS-URL client ids, the 2026-07-28 successor to Dynamic Client Registration — which remains supported for older clients).

​
MCP Endpoint

Health check: https://mcp.scrapebadger.com/health