--- title: Fetch Woodpecker Campaign Stats Via Claude Code MCP category: MCP Integrations publishDate: 2026-06-28T00:00:00.000Z --- ## The Problem Statement The cognitive load of switching between an AI assistant like Claude or Cursor and the Woodpecker dashboard is a productivity killer for growth engineers. Context switching breaks flow. You are in the middle of writing a complex prompt for a new feature, then you realize you need to check if your latest outreach campaign is still hitting its reply rate targets. Suddenly, you are navigating tabs, logging into Woodpecker, and digging through menus. This "dashboard fatigue" isn't just annoying; it's expensive. Every time you leave your primary development or research environment to check a secondary metric, you lose momentum. For B2B sales teams and growth engineers, the goal is to stay in the flow of execution, not to become professional dashboard navigators. The thesis here is simple: Integrating Woodpecker with an AI agent via MCP transforms cold email from a "check-and-react" manual process into a proactive, conversational management layer. You don't go to the data; you bring the data to your conversation. --- ## Technical Evidence The power of this integration lies in how natural language queries map directly to Woodpecker's API capabilities through Vinkius Edge. When you use an MCP-compatible client like Claude Desktop, Cursor, or Windsurf, you aren't just sending text; you are triggering precise operational tools. Let's look at a real-world sequence of how this works in practice. Imagine you are monitoring your outreach performance during a deep work session. ### Scenario: Investigating a Campaign Dip You notice a notification in your Vinkius Guardian Control Plane suggesting a potential drop in engagement. Instead of opening Woodpecker, you simply ask your AI assistant: **User Prompt:** "Show me the recent stats for my 'Q3 SaaS Founder' campaign." **The Agent's Execution (via Woodpever MCP):** The agent identifies the `get_campaign_stats` tool and executes it with the relevant ID. ```json // Internal Tool Call { "tool": "get_campaign_stats", "arguments": { "id": "campaign_q3_saas_founders" } } ``` **Agent Response:** "Campaign 'Q3 SaaS Founders' is showing a 4% reply rate, which is down from the usual 12%. Open rates are steady at 65%, but bounce rates have spiked to 8%." The drop in reply rate is now visible without you ever leaving your IDE. Because you can see this spike, you can immediately follow up with a corrective action: **User Prompt:** "That's too high. Check if any new prospects were added recently that might be causing bounces, and then pause the campaign so we don't ruin our sender reputation." **The Agent's Execution:** ```json // Sequential Tool Calls [ { "tool": "list_prospects", "arguments": { "campaign_id": "campaign_q3_saas_founders" } }, { "tool": "pause_campaign", "arguments": { "id": "campaign_q3_saas_founders" } } ] ``` **Agent Response:** "I've reviewed the recent prospects. It looks like several invalid emails were added in the last batch. I have successfully paused the 'Q3 SaaS Founders' campaign to protect your deliverability." This sequence demonstrates that the MCP server isn't just a read-only window; it is an operational bridge. You are using natural language to orchestrate complex, multi-step workflows that would otherwise require manual clicks and careful monitoring in the Woodpeker UI. --- ## Honest Limitations & Tradeoffs No tool is a silver bullet, and the Woodpecker MCP server has its specific friction points. First, there is the initial setup cost. While Vinkius makes the connection seamless via the App Catalog, you still need to generate an API key from your Woodpecker account (Settings → API keys). It's a one-time task, but it is a manual step that requires you to have access to the original platform. Second, the effectiveness of the agent is heavily dependent on your prompting. While the agent can execute `list_campaigns` or `add_prospect`, it cannot "guess" which campaign you mean if you haven't provided context in your current session. If you ask "How is my campaign doing?", and you have ten active campaigns, the agent will need to list them all first to find the right one. For complex, multi-step sequences--like updating a whole batch of prospects--you must provide structured, clear instructions to avoid errors. Finally, this integration is optimized for monitoring and rapid response, not deep configuration. If you need to redesign your entire 7-step email sequence with custom HTML templates, the Woodpecker dashboard remains the superior tool. The MCP server is your "command center" for oversight and quick adjustments; the dashboard remains your "workshop" for heavy lifting. --- ## Decision Framework How do you decide when to use the Woodpecker MCP server versus the native dashboard? Use this framework: ### Use the Woodpecker MCP Server When: - **You are monitoring performance:** Checking reply rates, open rates, or bounce metrics during your workday. - **You need rapid intervention:** Pausing a campaign that is behaving erratically or adding urgent prospects to an active sequence. - **You want proactive alerts:** Using the Vinkius Guardian Control Plane to trigger automated checks via your AI agent. - **You are working in an IDE:** Managing outreach while simultaneously coding or writing marketing copy in Cursor or VS Code. ### Stick to the Woodpecker Dashboard When: - **Performing deep configuration:** Setting up complex, multi-step follow-up sequences with intricate logic. - **Managing email templates:** Writing and testing HTML/plain text templates for your campaigns. - **Bulk account management:** Performing heavy administrative tasks that involve large-scale changes across many different accounts or settings. By treating the Woodpecker MCP server as a conversational layer on top of your existing workflow, you can maintain your focus, reduce context switching, and turn your outreach from a manual chore into an automated, intelligent process. Find the Woodpecker MCP server in the [Vinkius App Catalog](https://vinkius.com/apps/woodpecker-mcp).