MODEL CONTEXT PROTOCOL (MCP)

On-brand email campaigns
straight from your own AI

Your Claude. Your Cursor. Your Copilot. Alpaco MCP connects the AI tools you already use directly to your locked Email Design System—build campaigns in seconds, brand rules enforced automatically. No copy-pasting. No broken HTML. No fixes needed.

See how to it works
Claude Desktop Live Session
MCP CONNECTED
Any AI

Claude, Cursor, Copilot, ChatGPT

0

Brand Rule Violations Ever

80%

Campaign Foundation in Seconds

Unlimited Design System Queries

Brand Guardrail Engine

Enforcement Status — Active
LOCKED
Generic AI Without MCP

Generates raw <table> tags with arbitrary inline CSS, unapproved hex colors, and missing MSO conditional comments. Breaks Outlook rendering.

Alpaco MCP Protocol

AI requests assemble(template_id, blocks[]). Alpaco validates brand tokens, locks margins, and renders 100% compliant HTML verified across 80+ email clients.

DETERMINISTIC BRAND SAFETY

Brand guardrails built as the core feature

The MCP never lets an AI write raw HTML. Every call routes through Alpaco's locked design system. Models act as architects—picking approved components—while our deterministic engine compiles 100% cross-client compliant code every time.

Impossible to break brand rules

Constrained at a structural level. Vague prompts still produce compliant output.

422 self-correction guardrail loop

If the AI misses a required field, The Alpaco MCP works with your model to self-correct its payload instantly.

NO SURPRISE BILLS

Unlimited access with predictable budgeting

Alpaco does not track your interactions with a secondary usage meter or hit you with a separate volume-based bill. Enjoy completely unlimited access to the MCP gateway—scale automated workflows as aggressively as needed with total budget control.

You pay only your existing LLM provider (Anthropic, OpenAI, Microsoft) for the prompt tokens consumed in your AI client. That's it.

UNLIMITED THROUGHPUT ZERO SECONDARY TAX
0
Secondary Volume Meters
Design System Queries
High Context-Density Schemas

Tool definitions consume less than 4% of a standard Claude 3.5 Sonnet context window—your LLM budget goes further.

cursor-agent ~ mcp-exec
LIVE RPC
> User: "Assemble a newsletter with our top 3 winter products."
[MCP] Calling: templates()
[MCP] Found: 4 templates available
[MCP] Calling: assemble({ template_id, blocks[] })
[MCP] Layout assembled. Running brand token validation...
✓ Brand check passed: 0 warnings, 0 invalid styles.
→ Campaign ready. Preview: alpaco.email/preview/camp_84920
EXTENSIBLE TOOLCHAIN

Works in every AI tool your team already uses

Alpaco MCP plugs natively into any MCP-compliant client. Whether marketers are chatting through Claude or Slack bots, or developers are wiring up headless agents via Cursor and CI/CD pipelines—Alpaco adapts completely.

Claude Cursor ChatGPT Microsoft Copilot Google Gemini Slack Bots Custom Agents CI/CD Pipelines + any MCP client
DEVELOPER QUICKSTART

Two ways to connect with zero manual HTML

Alpaco MCP supports two integration tracks. Choose the method that best fits your workspace environment.

A

OAuth Authentication

Method 1 • Zero-token track (Admin only)
RECOMMENDED

The automated zero-token track managed through our secure authentication bridge. Validates commands via live browser handshake with your active Alpaco workspace.

1 Log into Alpaco and go to Organization Settings (Admin role required)
2 Create an MCP connection and note down your Client ID and Client Secret
3 Open your AI client and enter the Remote Server URL (.../api/mcp/v1/gateway), Client ID, and Client Secret
B

Manual Setup (JWT)

Method 2 • Advanced / Headless Agents
CODE CONFIG

For custom background scripts, persistent workflows, or AI clients connecting manually via Streamable HTTP (Server-Sent Events / SSE).

{
  "mcpServers": {
    "alpaco": {
      "url": "https://platform.alpaco.email/api/mcp/v1/gateway",
      "headers": {
        "Authorization": "Bearer YOUR_JWT_TOKEN"
      }
    }
  }
}
{
  "name": "alpaco",
  "type": "sse",
  "serverUrl": "https://platform.alpaco.email/api/mcp/v1/gateway",
  "env": {
    "ALPACO_JWT_TOKEN": "${ALPACO_JWT_TOKEN}"
  }
}
# 1. Grab your JWT from User Profile > Generate token
export ALPACO_JWT_TOKEN="your_generated_jwt_token"

# 2. Connect via Claude CLI (Streamable HTTP / SSE)
claude mcp add alpaco --transport sse \
  https://platform.alpaco.email/api/mcp/v1/gateway \
  --header "Authorization: Bearer $ALPACO_JWT_TOKEN"
Token: User Profile → Generate token
Endpoint: .../api/mcp/v1/gateway (SSE)

Different AI LLM's have different places/names for these settings. Check out the full Alpaco MCP Integration Guide →

WHAT YOU CAN DO

Ask in Plain English and Alpaco Executes

|

Instant Discovery

Alpaco returns your approved brand templates, allowed block types, and design rules with zero hallucinated components.

READY TO CONNECT YOUR AI?

Scale Email Production with Absolute Governance

Bring order to the herd. Enable your AI agents to build production-ready email campaigns safely within your enterprise design system.