← All integrations

Woodpecker Co MCP server

8 operations0 webhooks

Cold email and LinkedIn outreach with Woodpecker - list, run, pause and stop campaigns, remove unused campaign steps, add prospects to campaigns and read them back, and look up webhook event types.

Try Woodpecker Co with your agent

Connect Woodpecker Co, 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 Woodpecker Co on my account, then run one read-only example and show me the result.

Runs once, when you ask

Woodpecker Co tools and triggers

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

Campaigns

  • Delete StepDestructive

    Permanently delete an unused EMAIL or LINKEDIN step that is not the first step; the campaign must be DRAFT or EDITED

    campaigns.deleteStep

  • ListRead-only

    List campaigns, optionally filtered by status or ID; asking for exactly one ID also returns its statistics

    campaigns.list

  • PauseWrite

    Pause a campaign: no further contact with prospects until it is run again

    campaigns.pause

  • RunWrite

    Start or resume a campaign: it becomes RUNNING and Woodpecker starts contacting its prospects

    campaigns.run

  • StopWrite

    Stop a campaign: no further contact with prospects until it is run again

    campaigns.stop

Prospects

  • Add To CampaignWrite

    Add up to 20,000 prospects to a campaign, also creating them in the global list; each result says if that prospect was a duplicate or rejected

    prospects.addToCampaign

  • List In CampaignsRead-only

    List the prospects in one or more campaigns with their campaign status and interest level, with filters, sorting and paging

    prospects.listInCampaigns

Webhooks

  • List EventsRead-only

    List the event types Woodpecker can send to a webhook, from Woodpecker's docs; makes no API call

    webhooks.listEvents

Connect Woodpecker Co to Claude, ChatGPT or Cursor

  1. 1

    Connect Woodpecker Co in Corsair

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

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Woodpecker Co. On a ChatGPT personal plan, connect Woodpecker Co 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, Woodpecker Co's read and write operations run right away and its 1 destructive operation waits 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/woodpeckerco, add the Woodpecker Co plugin, and connect with an API key. Then call methods like corsair.woodpeckerco.api.campaigns.deleteStep() from your app. Corsair keeps each tenant isolated.

Yes. Woodpecker Co requires an API key from your Woodpecker Co 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 Woodpecker Co, GitHub, Notion, Stripe, and the rest. Trigger Woodpecker Co from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for cold email and linkedin outreach with woodpecker - list, run, pause and stop campaigns, remove unused campaign steps, add prospects to campaigns and read them back, and look up webhook event types. Common builds include sync jobs, admin tooling, and agents that call Woodpecker Co APIs from your backend.

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 Woodpecker Co 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/woodpeckerco in the open repo. When Woodpecker Co 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 Woodpecker Co data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Woodpecker Co 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 Woodpecker Co 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 1 destructive Woodpecker Co operation. You can change a link's mode at hub.corsair.dev/me.