Bring Zero Party Data
to CrewAI
Learn how to connect Fairing to CrewAI and start using 12 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 Fairing MCP Server?
Connect your Fairing (formerly EnquireLabs) account to any AI agent and take full control of your post-purchase surveys and zero-party data through natural conversation.
What you can do
- Survey & Question Management — List all active questions and fetch detailed configurations for your post-purchase surveys
- Response Tracking — List and inspect individual survey responses to understand customer sentiment and attribution
- Zero-Party Data Analysis — Query customer-specific responses to pair survey data with your marketing profiles
- Aggregated Insights — Extract high-level insights and performance metrics across all your survey streams
- Integration Audit — Monitor active integrations with platforms like Klaviyo, GA4, and Meta directly from the cloud
- Account Context — Retrieve your Fairing account details and API token identity flawlessly
How it works
1. Subscribe to this server
2. Enter your Fairing API Key (found in Settings > Account)
3. Start managing your customer insights from Claude, Cursor, or any MCP-compatible client
Who is this for?
- E-commerce Marketers — monitor customer attribution and survey performance without leaving your productivity tools
- Retention Specialists — review customer-specific feedback to personalize outreach and improve LTV
- Data Analysts — pull raw survey responses and insights directly into your AI-powered data workflow
Built-in capabilities (12)
Get Fairing account information
Get all survey responses for a specific customer
Get aggregated survey insights
Get current API token identity
Get details for a specific survey question
Get details for a specific survey response
Get details for a specific survey
List customers who have interacted with surveys
List active Fairing integrations
List all Fairing survey questions
List all survey responses
List all Fairing surveys
Why CrewAI?
When paired with CrewAI, Fairing becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Fairing 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
Fairing in CrewAI
Fairing and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Fairing 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 Fairing in CrewAI
The Fairing 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 12 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
Fairing for CrewAI
Every tool call from CrewAI to the Fairing 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 obtain my Fairing API Key?
You can find your API Key in the Fairing admin portal under Settings > Account. Note that API access may depend on your current subscription plan.
Can I see responses for a specific customer?
Yes! Use the get_customer_responses tool with the specific Customer ID to retrieve all survey feedback associated with that individual.
What kind of insights can I extract?
The get_insights tool provides aggregated data on question performance, response rates, and attribution trends across your survey streams.
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.