Bring Ad Server
to CrewAI
Learn how to connect AdButler 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.
What is the AdButler MCP Server?
Connect your AdButler account to any AI agent and take full control of your ad server orchestration and automated display advertising through natural conversation.
What you can do
- Campaign & Ad Portfolio Orchestration — List and manage your entire high-fidelity portfolio of advertisers and campaigns programmatically, retrieving detailed technical metadata
- Banner & Creative Intelligence — Programmatically retrieve directories of banners and access complete high-fidelity asset metadata to coordinate your organizational broadcasting
- Performance Architecture Monitoring — Access real-time status updates for active banners and track impression/click metrics directly through your agent
- Metadata Management — Programmatically retrieve high-fidelity zone IDs and publisher metadata to maintain a perfectly coordinated ad inventory record
- Operational Monitoring — Verify account-level API connectivity and monitor orchestration volume directly through your agent for perfectly coordinated service scaling
How it works
1. Subscribe to this server
2. Retrieve your API Key from your AdButler dashboard (Settings > API Access)
3. Start orchestrating your ad growth from Claude, Cursor, or any MCP client
No more manual checking of individual banner performance or missing campaign expiration alerts. Your AI acts as your dedicated ad coordinator and inventory architect.
Who is this for?
- Ad Ops Managers — instantly retrieve campaign summaries and monitor ad health using natural language commands
- Publishers — verify individual zone metadata and track inventory filling without leaving your creative workspace
- Developers — integrate high-speed AdButler data into custom dashboards and reporting tools through simple AI queries
Built-in capabilities (10)
Verify AdButler API connectivity
Get advertiser details
Get campaign details
Get ad serving statistics
List all advertisers
List ad items in a campaign
List all campaigns
List all placements
List all publishers
List all ad zones
Why CrewAI?
When paired with CrewAI, AdButler becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AdButler 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
mcpsparameter 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
AdButler in CrewAI
AdButler and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect AdButler 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for AdButler in CrewAI
The AdButler 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.
* 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
How Vinkius secures
AdButler for CrewAI
Every tool call from CrewAI to the AdButler MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my AdButler API Key?
Log in to your account, navigate to Settings > API Access, and copy your unique API Key from the credentials section.
Can I check ad performance via AI?
Yes! The get_stats tool retrieves impression and click data for all your active banners and campaigns.
How do I list my advertisers?
Use the list_advertisers tool to retrieve all advertiser profiles with their unique identifiers.
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.
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.
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.
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.
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.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
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.