Skip to content
Woodpecker logo

Woodpecker MCP server

Cold email automation tool for sales teams to send personalized outreach campaigns

Woodpecker is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
6
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the Woodpecker MCP server

Connect Woodpecker once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Woodpecker and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Woodpecker tools your AI can run

Once connected, your assistant can call any of these Woodpecker actions by asking in plain language.

  • Create/Update Prospect in Campaign

    Adds a new prospect or updates existing prospect data in a campaign

    20 fields

  • Create/Update Prospect

    Adds a new prospect or updates existing prospect in the global prospect list

    19 fields

  • Blacklist Domain

    Add a domain to the blacklist to block sending to all prospects within that domain

    1 field

  • Get Prospect Responses

    Fetch all responses from a specified prospect

    2 fields

  • Find Prospect by Email

    Search for a prospect by their email address

    2 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Woodpecker events your agent can watch

These start a run the moment something happens in Woodpecker, so work gets picked up on its own.

  • Prospect Replied

    Triggers when a prospect replies to an email or their status is manually set to RESPONDED

  • Prospect Blacklisted

    Triggers when a prospect is added to the blacklist

  • Prospect Opt-out

    Triggers when a prospect opts out from receiving emails

  • Prospect Bounced

    Triggers when an email to a prospect bounces

  • Prospect Invalid

    Triggers when a prospect email is marked as invalid

  • Prospect Autoreplied

    Triggers when an autoreply is detected from a prospect

  • Prospect Saved

    Triggers when a prospect is saved

  • Prospect Nonresponsive

    Triggers when a prospect is marked as nonresponsive

  • Prospect Clicked a Link

    Triggers when a prospect clicks a link in an email

  • Prospect Opened an Email

    Triggers when a prospect opens an email

  • Prospect Interested

    Triggers when a prospect is marked as interested

  • Prospect Maybe Later

    Triggers when a prospect is marked as maybe later

  • Prospect Not Interested

    Triggers when a prospect is marked as not interested

  • Campaign Email Sent

    Triggers when a campaign email is sent to a prospect

  • Follow-up After Autoreply

    Triggers when a follow-up is scheduled after an autoreply

  • Secondary Replied

    Triggers when a secondary email address replies

  • Campaign Completed

    Triggers when a campaign is completed

  • Task Created

    Triggers when a task is created

  • Task Done

    Triggers when a task is marked as done

  • Task Ignored

    Triggers when a task is ignored

Give your assistant Woodpecker

Connect Woodpecker once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Woodpecker MCP, answered.

No. That is the point of it. One Activepieces server exposes Woodpecker alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Woodpecker in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 6 tools, including Create/Update Prospect in Campaign, Create/Update Prospect, Blacklist Domain, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.