Compatible with every major AI agent and IDE
What is the Taboola MCP Server?
Connect your Taboola Backstage account to any AI agent and take full control of your native advertising workflows through natural conversation.
What you can do
- Account Management — List all allowed accounts and retrieve current user profile details
- Campaign Control — List, fetch, create, and update campaigns including budgets, CPC, and active status
- Ad Management — Manage campaign items (ads) by listing existing creatives or adding new URLs and thumbnails
- Performance Reporting — Run detailed campaign summary reports by dimension (day, week, month) or identify top-performing content
How it works
- Subscribe to this server
- Enter your Taboola Client ID and Client Secret
- Start optimizing your native ads from Claude, Cursor, or any MCP-compatible client
No more jumping between tabs to check CTR or adjust daily caps. Your AI acts as a dedicated Ad Ops specialist.
Who is this for?
- Digital Marketers — instantly retrieve performance metrics and adjust campaign settings without opening Backstage
- Ad Ops Teams — automate the creation of campaign items and monitor account access across multiple clients
- Growth Engineers — integrate real-time ad performance data into development workflows for faster iteration
Built-in capabilities (10)
Create a new Taboola campaign
Create a new campaign item (ad)
Get details for a specific campaign
Get campaign summary report
Get current Taboola user details
Get top campaign content report
List allowed Taboola accounts
List items (ads) in a campaign
List campaigns for an account
Update an existing Taboola campaign
Why CrewAI?
When paired with CrewAI, Taboola becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Taboola 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
Taboola in CrewAI
Taboola and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Taboola 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 | 4,000+ 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 Taboola in CrewAI
The Taboola 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
Taboola for CrewAI
Every tool call from CrewAI to the Taboola MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see how my campaigns are performing across different time periods?
Yes! Use the get_campaign_summary_report tool. You can specify the account_id and a dimension (like day, week, or month) to get a detailed breakdown of metrics like clicks, impressions, and spend.
How do I add a new ad to an existing campaign?
Simply use the create_campaign_item action. Provide the account_id, campaign_id, and the url of the content you want to promote. You can also optionally include a custom title and thumbnail URL.
Is it possible to pause or update the budget of a campaign?
Yes. The update_campaign tool allows you to modify the daily_cap, cpc, and the is_active status of any campaign by providing its ID and the target account ID.
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.
Explore More MCP Servers
View all →
Coppel
14 toolsAutomate retail operations via Coppel — browse products, manage orders, check customer credit, and find stores across Mexico from any AI agent.

OceanBase
10 toolsEnterprise distributed relational database — manage clusters, tenants, and databases via AI.

Vimeo
10 toolsManage your Vimeo account — audit videos, folders, and showcases via AI.

Truto Unified Calendar
10 toolsEmpower your AI agent with a universal API to read, schedule, and sync events seamlessly across Google, Outlook, and other major calendar providers.
