Scrapling MCP Server vs Tinysearch

A side-by-side look at the Scrapling MCP Server and Tinysearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Scrapling MCP Server logoScrapling MCP ServerSearch & Data Extraction · Local subprocess (stdio)Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.51GoodAuth: no auth requiredTinysearch logoTinysearchSearch & Data Extraction · Local subprocess (stdio)Self-hosted web research for MCP agents.43FairAuth: not declared

Verdict: choose Scrapling MCP Server for search & data extraction work as a local process; choose Tinysearch for search & data extraction as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Scrapling MCP Server logoChoose Scrapling MCP Server when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Scrapling MCP Server

Tinysearch logoChoose Tinysearch when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
Explore Tinysearch

Feature & specification comparison

Rows where the two servers differ are marked.

SpecScrapling MCP Server logoScrapling MCP ServerTinysearch logoTinysearch
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal51/100 · Good43/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars89,349234
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Scrapling MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Tinysearch tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Scrapling MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "scrapling-mcp-server": {
      "command": "uvx",
      "args": [
        "scrapling"
      ]
    }
  }
}

Tinysearch

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tinysearch": {
      "command": "uvx",
      "args": [
        "--from",
        "tinysuite-search[server]",
        "tinysearch"
      ]
    }
  }
}

Frequently asked questions

Scrapling MCP Server is categorized under Search & Data Extraction and uses a local stdio subprocess. Tinysearch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Scrapling MCP Server for search & data extraction work and Tinysearch for search & data extraction.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Scrapling MCP Server is listed as free. Auth: no auth required. Tinysearch has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add scrapling-mcp-server and tinysearch as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Scrapling MCP Server has a quality signal of 51/100 (Good) with 4 views, 0 installs and 89,349 GitHub stars. Tinysearch has 43/100 (Fair) with 2 views, 0 installs and 234 GitHub stars.