MCP Server Overview
CampaignStack exposes its entire platform through the Model Context Protocol (MCP). The MCP server provides 200+ tools across 30 domains, giving AI agents full programmatic access to campaigns, leads, workflows, content, outreach, inbox, and more.
Architecture
Section titled “Architecture”AI Agent / MCP Client │ ▼ MCP Server (port 3002) ├── Auth: API key validation + scope check ├── Validation: Zod .strict() input schemas └── Backend: Convex (serverless) └── Runner (LinkedIn automation)The server is hosted at https://mcp.campaignstack.io/mcp (Streamable HTTP, API key auth) — see Transports.
Tool domains
Section titled “Tool domains”| Domain | Tools | Description |
|---|---|---|
| Campaigns | 7 | Create, list, get, update, archive, delete campaigns |
| Personas & Phases | 10 | Buyer personas and campaign roadmap phases |
| Leads | 7 | Search, get, import CSV, contact info, platform profile linking |
| Lead Lists | 8 | Static and query-based lists, add/remove leads |
| Companies | 3 | Company lookup and company signals |
| ICPs | 6 | ICP CRUD, scoring triggers, score breakdowns |
| Enrichment | 3 | Queue leads, priority enrich, enrichment status |
| Workflows | 8 | Create, update, trigger, node vocabulary |
| Workflow Execution | 6 | Stats, leads at node, activity, retry, requeue |
| Workflow Nodes | 4 | Complete, fail, store conversations, escalate |
| Workflow Review | 6 | Human-in-the-loop approve/reject/edit |
| Split Optimization | 2 | A/B split re-weighting and optimization logs |
| Craft | 5 | AI-powered message, note, comment, followup, reply writing |
| Content | 17 | Post lifecycle, scheduling, brand voice, analytics, calendar |
| Outreach | 5 | Connection request, InMail, like, comment, follow |
| Inbox | 6 | Conversations, messages, unread counts |
| Signals | 4 | Lead score breakdown, signal weights |
| Signal Agents | 10 | Audience agents: CRUD, stats, leads |
| Signal Exclusions | 5 | Exclusion lists and opt-outs |
| Competitors | 6 | Company/profile monitoring watches |
| Topics & Search Watches | 3 | Search topics and saved search watches |
| LinkedIn Accounts | 6 | Accounts, connections export, private proxies |
| Google Services | 12 | Gmail sending, calendar, email warmup |
| Integrations | 7 | Apollo, Instantly, webhook templates |
| Automations | 4 | List, toggle, job history |
| Workspace | 13 | Members, invitations, settings, branding, playbook |
| Metrics & Billing | 4 | Campaign/workspace metrics, credit balance |
| Notifications | 6 | List, mark read, preferences |
| Search & Diagnostics | 4 | Search URL builder, sourcing diagnosis, post engagement, website analysis |
| Admin | 14 | Blog and feature flag management (platform admins only) |
Design principles
Section titled “Design principles”- JSON-only responses — all tool output is structured JSON, never markdown
- Cross-referenced errors — error messages suggest which tool to call next
- Strict validation — Zod
.strict()rejects unknown input fields - MCP annotations — every tool declares
readOnlyHint,destructiveHint,idempotentHint - Actionable descriptions — tool descriptions reference related tools to help agents chain operations
Endpoints
Section titled “Endpoints”| Method | Path | Auth | Purpose |
|---|---|---|---|
GET | /health | None | Server status, version, tool list |
POST | /mcp | Bearer | MCP JSON-RPC messages |
GET | /mcp | Bearer | SSE stream for sessions |
DELETE | /mcp | Bearer | Close session |
Next steps
Section titled “Next steps”- Authentication — API keys and scopes
- Transports — HTTP connection details
- Tool Reference — Full tool documentation