Pulldata

io.pulldataPublished by pulldata.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Discover and run Pulldata scrapers, track jobs, and retrieve results from your AI client.

VerifiedSSEWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant discover and run Pulldata web scrapers, track scraping jobs, and retrieve their results.

What you can do
Pulldata exposes its scraping platform to an AI client over a remote SSE endpoint. According to the registry description, the assistant can discover available scrapers, run them, follow the status of the jobs it starts, and fetch the results. The manifest does not list individual tool names, so the exact operations are not documented here.
When to use it
Worth adding when you already use Pulldata and want an assistant to launch scrapers and pull their output without leaving the chat. It is aimed at collecting web data through Pulldata's hosted scrapers rather than writing custom scraping code.
Requirements
A remote MCP endpoint at reached over SSE; no local package or runtime is needed. A Pulldata live API key must be supplied in the x-api-key header. Network access to the endpoint is required.
Before you install
The x-api-key header carries a live Pulldata API key, so treat it as a secret and avoid exposing it in shared logs or transcripts. Running scrapers sends requests to third-party sites through Pulldata and may consume paid quota or credits on your account; check your plan before letting an assistant start jobs.

Installation

In SourceWeft

  1. Open Pulldata in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.pulldata%2Fpulldata/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pulldata": {
      "type": "sse",
      "url": "https://pdb.pulldata.io/api/mcp/sse",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 28, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.