Claude, Cursor, Copilot, ChatGPT
Brand Rule Violations Ever
Campaign Foundation in Seconds
Unlimited Design System Queries
Brand Guardrail Engine
Enforcement Status — ActiveGenerates raw <table> tags with arbitrary inline CSS, unapproved hex colors, and missing MSO conditional comments. Breaks Outlook rendering.
AI requests
assemble(template_id, blocks[]). Alpaco validates brand tokens, locks margins, and renders
100% compliant HTML verified across 80+ email clients.
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.
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.
Tool definitions consume less than 4% of a standard Claude 3.5 Sonnet context window—your LLM budget goes further.
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.
Two ways to connect with zero manual HTML
Alpaco MCP supports two integration tracks. Choose the method that best fits your workspace environment.
OAuth Authentication
Method 1 • Zero-token track (Admin only)The automated zero-token track managed through our secure authentication bridge. Validates commands via live browser handshake with your active Alpaco workspace.
.../api/mcp/v1/gateway), Client ID, and Client
Secret
Manual Setup (JWT)
Method 2 • Advanced / Headless AgentsFor 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"
.../api/mcp/v1/gateway (SSE)
Different AI LLM's have different places/names for these settings. Check out the full Alpaco MCP Integration Guide →
Ask in Plain English and Alpaco Executes
|
Alpaco returns your approved brand templates, allowed block types, and design rules with zero hallucinated components.