Bring Marketing Attribution
to CrewAI
Learn how to connect Northbeam 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.
GDPR Free for Subscribers
What is the Northbeam MCP Server?
Connect your Northbeam account to your AI agent and gain deep insights into your marketing performance and attribution data through natural conversation.
What you can do
- Metric Discovery — List all available performance metrics such as Attributed Revenue, Transactions, and Spend.
- Data Breakdowns — Access the labels used to group your data, including Platform, Campaign, Ad Set, and more.
- Attribution Modeling — View supported attribution models to understand how credit is assigned across touchpoints.
- Programmatic Exports — Initialize new data exports for specific date ranges and sets of metrics.
- Export Monitoring — Track the status of your active data exports and retrieve direct download URLs for results.
- Workspace Oversight — Monitor active webhooks, scheduled recurring exports, and recent export history.
- Account Insights — Access high-level configuration, dashboard settings, and authenticated account metadata.
How it works
1. Subscribe to this server
2. Enter your Northbeam API Key and Data Client ID
3. Start analyzing your marketing attribution from Claude, Cursor, or any MCP client
Who is this for?
- Marketing Managers — quickly check available metrics or export statuses without opening the Northbeam dashboard.
- Data Analysts — automate the retrieval of complex attribution data for deeper reporting and modeling.
- Growth Teams — monitor recently completed exports and verify data synchronization in real-time.
Built-in capabilities (10)
Initialize a new data export
Get account metadata
Get workspace dashboard settings
Check data export status
g., Clicks only, Modeled). List supported attribution models
g., Platform, Campaign, Ad Set) in attribution reports. List available data breakdowns
g., Attributed Revenue, Transactions, Spend) available for export. List available attribution metrics
List recently completed exports
List scheduled data exports
List active webhooks
Why CrewAI?
When paired with CrewAI, Northbeam becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Northbeam 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
Northbeam in CrewAI
Northbeam and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Northbeam 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 Northbeam in CrewAI
The Northbeam 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
Northbeam for CrewAI
Every tool call from CrewAI to the Northbeam MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Where do I find my Northbeam API credentials?
Log in to your Northbeam Dashboard, navigate to Settings > API Keys. You will find both your API Key and your Data-Client-ID (UUID) there.
Can I download data directly through the agent?
Yes! The get_export_status tool will provide a direct download URL once the export status is marked as 'SUCCESS'.
How do I know which metrics I can export?
Use the list_metrics and list_breakdowns tools to see all valid parameters available for your account before creating a new data export.
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.