PulpMiner

Overview

PulpMiner MCP server is an integration service provided by PulpMiner that connects Model Context Protocol (MCP) clients to PulpMiner's web scraping and API generation platform. It allows AI assistants such as Claude and Cursor to extract structured JSON data from web pages directly within conversational chat interfaces. Users can also convert extracted data structures into reusable, hosted API endpoints without leaving their development environment.

Key Features

• Natural language web extraction — Converts arbitrary web pages into structured JSON schemas specified directly via plain-text prompts.
• API endpoint generation — Saves extracted web data structures as persistent HTTP endpoints with customizable URL path variables and caching support.
• JavaScript rendering execution — Provides rendering options to handle JavaScript-heavy websites during extraction and subsequent API calls.
• Saved endpoint retrieval — Calls previously created PulpMiner API endpoints directly from the assistant to refresh structured web data on demand.
• Flexible deployment architecture — Runs as a remotely hosted MCP server URL or locally on developer machines via the pulpminer-mcp npm package.
• Stateless authentication — Forwards API keys or OAuth sessions directly to the PulpMiner API without storing credentials on the MCP server.

Who It's For

The tool is designed for software developers, data engineers, and technical researchers working inside MCP-compatible environments such as Cursor and Claude. It suits teams seeking rapid prototyping for data extraction pipelines without manually authoring and maintaining bespoke web scrapers. Organizations using automation tools like Zapier and n8n can also use the service to generate REST endpoints quickly for downstream consumption.

Notable Strengths

PulpMiner stands out by bridging conversational scraping directly into persistent, production-ready REST endpoints that operate independently of the chat environment. Its dual deployment design enables both zero-install hosted connectivity and local npm execution while maintaining a strictly stateless architecture that does not retain user API keys. Additionally, usage costs are managed through transparent, per-operation credits that do not expire over time.