Webalza docs
Webalza runs your client pipeline — find leads with outdated sites, pitch each one with a redesign demo built for them, and run the outreach. Two agent surfaces cover it end to end: WebAlza Mate, the agent built into the dashboard, and the MCP server, which puts the same powers into your own AI agent.
Start here
The agent built into Webalza: capabilities, the plan-approval safety model, and FAQ.
Wire Claude, Codex, Cursor or any MCP-capable agent into your workspace in minutes.
Connect your agent in 30 seconds
Every MCP client connects to the same streamable-HTTP endpoint. Point your agent at it, sign in once, and it can manage campaigns, leads, inbox, audiences and more:
Server URL
https://server.webalza.com/api/mcp
- 1Copy the server URL above and add it to your agent's MCP configuration (or run the one-line command from the MCP doc).
- 2Sign in with OAuth or paste an API key from Dashboard → Connect Your Agent → API Keys.
- 3Ask your agent something real — "create a LinkedIn campaign for Austin dentists with outdated sites".
Detailed per-agent guides — Claude, Codex, OpenCode, Antigravity, Cursor, ZCode and more — live in the MCP setup doc.
In the dashboard vs. in your agent
Both surfaces drive the same workspace and share the same plan limits and credit mechanics — pick whichever is in front of you:
- Mate lives in the dashboard chat — plans, approvals and results in one thread, with a visual plan card before anything sends.
- Your own agent connects over MCP — same tools, your model, your terminal or editor. Usage over MCP is free; you pay your model provider.
- Credit-bearing actions (campaign sends, website redesigns) consume plan credits either way, and plan abilities decide which tools appear.
All docs
Get started