Bring Zero Party Data
to Cursor
Learn how to connect Fairing to Cursor 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 Cursor?
Cursor's Agent mode turns Fairing into an in-editor superpower. Ask Cursor to generate code using live data from Fairing and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Fairing in Cursor
Fairing and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Fairing to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.