Woodpecker MCP Server

Created By
a year ago
The Woodpecker MCP (Model Context Protocol) integration transforms cold email campaign management into a conversational experience.
Overview

What is Woodpecker MCP Server?

The Woodpecker MCP (Model Context Protocol) Server integrates with Woodpecker's automation platform to transform cold email campaign management into a conversational experience, allowing users to manage campaigns through natural language interactions.

How to use Woodpecker MCP Server?

To use the Woodpecker MCP Server, connect it to your AI assistant and issue commands to create, manage, and optimize email campaigns. Ensure you have a Woodpecker account and the necessary API credentials.

Key features of Woodpecker MCP Server?

  • Campaign Management: Create, update, run, pause, and delete email campaigns.
  • Prospect Operations: Add and update prospects in campaigns.
  • Email Composition: Create multistep email sequences with A/B testing.
  • Analytics & Reporting: Retrieve campaign statistics and performance metrics.
  • Mailbox Integration: Assign email accounts to campaigns.
  • Advanced Configuration: Support for delivery schedules and GDPR compliance.

Use cases of Woodpecker MCP Server?

  1. Automating cold email outreach campaigns.
  2. Managing follow-up sequences based on recipient responses.
  3. Analyzing campaign performance to optimize outreach strategies.

FAQ from Woodpecker MCP Server?

  • Can I use Woodpecker MCP Server with any AI agent?

Yes, as long as the agent supports the Model Context Protocol.

  • Do I need Woodpecker account to use this integration?

Yes, Woodpecker account with API access is required.

  • How do I troubleshoot connection issues?

Check Docker installation, API key validity, and ensure the MCP server is running.

Server Config

{
  "mcpServers": {
    "woodpecker": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "WOODPECKER_API_KEY",
        "woodpeckerco/woodpecker-mcp-server"
      ],
      "env": {
        "WOODPECKER_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
-
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago