Skip to main content
The PulpMiner MCP server gives AI assistants the same powers you have in the dashboard. Ask in plain words and the assistant can turn a web page into JSON, save it as an API, and call your saved APIs for fresh data. It works with any client that speaks the Model Context Protocol, including Claude, Claude Desktop and Cursor.

What you can ask for

Once connected, you can say things like:
  • “Get the title, author, price and rating from copperbooks.com/books/field-notes-on-copper as JSON.”
  • “Save that as an API, with the book slug as a variable.”
  • “Call my Copper Books API for the-salt-road and summarise the reviews.”
  • “Which PulpMiner APIs do I have saved?”
The assistant picks the right tool, runs it, and shows you the result.

Connect

You can use the hosted server, which needs no install, or run the npm package on your own machine. Point your client at https://mcp.pulpminer.com/mcp. Clients that support OAuth will ask you to sign in with your PulpMiner account. Clients that don’t can send your API key instead.
  1. Open Settings → Connectors and choose Add custom connector.
  2. Name it PulpMiner and paste the URL https://mcp.pulpminer.com/mcp.
  3. Select Connect and sign in with your PulpMiner account.
Your API key is only forwarded to the PulpMiner API to run the tool you asked for. The MCP server never stores it.

Local server (npm)

Run the server on your own machine with npx. This needs Node.js 18 or later and your API key in the PULPMINER_API_KEY environment variable.
In Claude Desktop the file is claude_desktop_config.json, which you can open from Settings → Developer → Edit Config. Restart the app after saving it. You’ll find your API key in the dashboard. See API Keys for details.

Tools

Credits are the same as in the dashboard. See Credits.

Options

pulpminer_generate_json and pulpminer_save_as_api accept the same settings as the Generate API screen: pulpminer_save_as_api also takes cache, which serves cached JSON for up to 24 hours and refreshes it in the background once it’s more than 15 minutes old.

A typical session

1

Preview the JSON

The assistant calls pulpminer_generate_json with the URL, plus a sample shape if you described one, and shows you the result.
2

Save it as an API

When you’re happy with the shape, pulpminer_save_as_api saves it and returns the endpoint, for example https://api.pulpminer.com/external/566.
3

Call it whenever you need fresh data

pulpminer_fetch_api_data calls the API by its ID. For a dynamic API, pass the variables, for example { "slug": "the-salt-road" }.
The saved API is a normal PulpMiner endpoint. It shows up in your Saved APIs and you can call it from your own code too. See API Endpoints.

Troubleshooting

Check that the API key is copied in full from the dashboard, and that you send it as Authorization: Bearer YOUR_API_KEY with no extra quotes. Ask the assistant to run pulpminer_check_api_key to confirm.
Ask the assistant to try scraper_2, to turn on renderJs for pages that load their content with JavaScript, or to narrow the page with a selector.
Reading a page with JavaScript rendering and AI can take tens of seconds. Saving the API with cache turned on makes repeat calls answer much faster.
Need help? Email hello@pulpminer.com or open an issue on GitHub.