← All integrations

ParseHub MCP server

8 operations0 webhooks

Run ParseHub scraping projects and get the data they extract.

Try ParseHub with your agent

Connect ParseHub, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in ParseHub on my account, then run one read-only example and show me the result.

Runs once, when you ask

ParseHub tools and triggers

Tools are what your agent can do in ParseHub through Corsair's MCP server. Triggers are the ParseHub events a routine can start from.

Projects

  • GetRead-only

    Get one project with its last run, last ready run and the 20 most recent runs.

    projects.get

  • Get Last Ready DataRead-only

    Get the extracted data of the most recent run of a project that has data ready.

    projects.getLastReadyData

  • ListRead-only

    List the scraping projects on the ParseHub account, 20 at a time.

    projects.list

  • RunDestructive

    Start a run of a project on the ParseHub cloud. Returns the new run; poll runs.get until data_ready.

    projects.run

Runs

  • CancelDestructive

    Cancel a running run. Data extracted so far stays available.

    runs.cancel

  • DeleteDestructive

    Delete a run and its data, cancelling it first if it is running.

    runs.delete

  • GetRead-only

    Get one run: status, data_ready, page count and timing.

    runs.get

  • Get DataRead-only

    Get the data a run extracted, as JSON or CSV.

    runs.getData

Connect ParseHub to Claude, ChatGPT or Cursor

  1. 1

    Connect ParseHub in Corsair

    Add your ParseHub API key once in Corsair. Corsair stores the credential encrypted and makes the ParseHub API calls for your agent, so it never goes into a prompt or a config file. Connect ParseHub

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs ParseHub. On a ChatGPT personal plan, connect ParseHub here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, ParseHub's read and write operations run right away and its 3 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/parsehub, add the ParseHub plugin, and connect with an API key. Then call methods like corsair.parsehub.api.projects.get() from your app. Corsair syncs data per tenant.

Yes. ParseHub requires an API key from your ParseHub account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit ParseHub, GitHub, Notion, Stripe, and the rest. Trigger ParseHub from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for run ParseHub scraping projects and get the data they extract. Common builds include sync jobs, admin tooling, and agents that call ParseHub APIs from your backend. Local DB entities let you query synced ParseHub records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per ParseHub API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/parsehub in the open repo. When ParseHub ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your ParseHub data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store ParseHub data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put ParseHub on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 3 destructive ParseHub operations. You can change a link's mode at hub.corsair.dev/me.