4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Unbounce MCP Server

Bring Landing Pages
to CrewAI

Learn how to connect Unbounce to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get LeadGet MeGet PageList AccountsList DomainsList Form FieldsList LeadsList Page GroupsList PagesList Sub Accounts

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Unbounce

What is the Unbounce MCP Server?

Connect your Unbounce account to any AI agent and simplify how you manage your conversion-focused landing pages, lead data, and custom domains through natural conversation.

What you can do

  • Landing Page Control — List and inspect all landing pages across your sub-accounts and retrieve detailed configuration metadata.
  • Lead Analysis — List and query all leads submitted through your forms, and retrieve individual lead data for processing.
  • Domain Oversight — List custom domains registered in your account to verify connectivity and SSL status.
  • Account Organization — Manage sub-accounts and page groups to keep your marketing assets structured.
  • Form Insight — List all form fields across page variants to understand your data collection points.
  • User Monitoring — Fetch account details and verify your current Unbounce user profile.

How it works

  1. Subscribe to this server
  2. Enter your Unbounce API Key (found in your account API management)
  3. Start managing your landing pages from Claude, Cursor, or any MCP client

Who is this for?

  • Marketing Managers — quickly check page performance and retrieve new leads via simple AI queries.
  • Web Developers — verify domain configurations and form field structures directly from the workspace.
  • Conversion Optimizers — get instant bird's-eye views of page groups and variant data via the AI assistant.

Built-in capabilities (10)

get_lead

Get details for a specific lead

get_me

Get current Unbounce user details

get_page

Get details for a specific landing page

list_accounts

List all Unbounce accounts

list_domains

List custom domains

list_form_fields

List form fields for a page

list_leads

List leads for a page

list_page_groups

List page groups

list_pages

List pages for a sub-account

list_sub_accounts

List sub-accounts (clients)

Why CrewAI?

When paired with CrewAI, Unbounce becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Unbounce tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Unbounce in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Unbounce and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Unbounce to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Unbounce in CrewAI

The Unbounce MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unbounce
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Unbounce for CrewAI

Every tool call from CrewAI to the Unbounce MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I see all the leads collected by a specific landing page?

Yes! Use the list_leads tool and provide the Page ID. Your agent will retrieve the complete list of submissions for that page.

02

How do I list all landing pages in a sub-account?

Use the list_pages query with your Sub-Account ID. The agent will return all landing pages associated with that specific client or project area.

03

Is it possible to see the form fields used on a page via AI?

Absolutely. Run the list_form_fields query with your Page ID. The agent will retrieve all form fields defined across all variants of that landing page.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →