Woodpecker MCP Server

The Woodpecker MCP (Model Context Protocol) integration transforms cold email campaign management into a conversational experience. Exposed over MCP by the woodpecker mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• Campaign Management — Create, update, run, pause and delete email campaigns
• Prospect Operations — Add prospects to your account and campaigns, update and delete prospect data, search prospects
• Email Composition — Create multistep email sequences with A/B testing capabilities
• Analytics & Reporting — Retrieve campaign statistics and performance metrics
• Mailbox Integration — Assign email accounts to campaigns
• Advanced Configuration — Support for delivery schedules, timezone settings and GDPR compliance

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — The Prerequisites tool exposed by this server
• Troubleshooting — The Troubleshooting tool exposed by this server
• createCampaign — Create campaigns with basic configuration including subjects, messages and delivery settings. Supports full templating with snippets, fallbacks and
• createAdvancedCampaign — Create campaigns with full API capabilities including A/B testing and complex delivery schedules
• listCampaigns — The listCampaigns tool exposed by this server
• retrieveCampaignDetails — Get detailed campaign structure including all steps and configurations
• retrieveCampaignStatistics — The retrieveCampaignStatistics tool exposed by this server
• updateCampaignSettings — Modify campaign-wide settings including name, email accounts, daily limits and timezone
• buildCampaignUrl — The buildCampaignUrl tool exposed by this server
• addStep — The addStep tool exposed by this server
• updateCampaignStep — The updateCampaignStep tool exposed by this server
• updateStepVersion — Update email content, subject lines, signatures and tracking settings

Configuration

You will need 2 environment variables: WOODPECKER_API_KEY, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before setting up the integration, ensure you have: - Woodpecker Account: An account with the API & Integration add-on enabled - API Credentials: Woodpecker API key (found in your account settings) - Docker: Installed on your system (for running the MCP server) https://docs.docker.com/desktop/ - AI Agent: Claude Desktop, Continue.dev or another

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Woodpecker.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the woodpecker mcp server does with a few real requests.

When to reach for it

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Woodpecker's toolset — Prerequisites, Troubleshooting, createCampaign and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Woodpeckerco; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.