Bring Reputation Management
to Cursor
Learn how to connect Birdeye to Cursor and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Birdeye MCP Server?
Connect your Birdeye account to any AI agent and take full control of your online reputation management and customer experience workflows through natural conversation.
What you can do
- Review Orchestration — List and manage customer reviews across multiple platforms (Google, Facebook, etc.) programmatically, retrieving detailed high-fidelity comments and ratings in real-time
- Automated Check-ins — Programmatically trigger review requests (check-ins) via SMS or Email to coordinate high-fidelity feedback collection from your recent visitors
- Sentiment Intelligence — Access complete customer profiles and retrieve detailed sentiment history to maintain a perfectly coordinated overview of your brand health
- Survey & Feedback Architecture — Programmatically dispatch custom surveys to specific customers and monitor their high-fidelity responses directly through your agent
- Multi-Location Visibility — Retrieve complete directories of all your business branches and locations to coordinate your organizational reputation programmatically
How it works
1. Subscribe to this server
2. Retrieve your API Key and Business ID (bid) from your Birdeye dashboard (Settings > Integrations > API)
3. Start managing your customer experience from Claude, Cursor, or any MCP client
No more manual logging into individual review sites or missing critical feedback. Your AI acts as your dedicated reputation manager and customer success coordinator.
Who is this for?
- Marketing Managers — instantly retrieve high-level review summaries and monitor brand sentiment using natural language commands
- Customer Success Teams — automate the dispatch of review requests and track customer satisfaction without leaving your workspace
- Multi-Location Owners — monitor reputation performance across all branches and coordinate surveys through simple AI queries
Built-in capabilities (6)
Add a new customer profile
Trigger a review request (Check-in)
Get full customer profile
List all business locations
List customer reviews
Send a custom survey to a customer
Why Cursor?
Cursor's Agent mode turns Birdeye into an in-editor superpower. Ask Cursor to generate code using live data from Birdeye and it fetches, processes, and writes. all in a single agentic loop. 6 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
Birdeye in Cursor
Birdeye and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Birdeye 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 Birdeye in Cursor
The Birdeye 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 6 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
Birdeye for Cursor
Every tool call from Cursor to the Birdeye 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 Birdeye API Key and Business ID?
Log in to your account, navigate to Settings > Integrations > API, and you will find your API Key and the Business ID (bid).
Can I request a review via AI?
Yes! The customer_checkin tool allows your agent to record a customer visit and automatically send a review request via their preferred channel.
How do I check review ratings programmatically?
Use the list_reviews tool and provide an optional rating filter (1-5) to retrieve specific categories of feedback directly from the platform.
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.