Follow Up Boss MCP Server for CursorGive Cursor instant access to 12 tools to Add Internal Note, Create Followup Task, Create New Lead, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Follow Up Boss app connector for Cursor is a standout in the Real Estate category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Follow Up Boss and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"follow-up-boss-alternative": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About Follow Up Boss MCP Server
Connect your Follow Up Boss account to any AI agent and take full control of your real estate lead management and follow-up workflows through natural conversation.
Cursor's Agent mode turns Follow Up Boss into an in-editor superpower. Ask Cursor to generate code using live data from Follow Up Boss 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.
What you can do
- Lead Orchestration — List and manage your complete database of people and leads, including retrieving detailed contact profiles and communication history
- Activity Monitoring — Track real-time events such as website registrations, property inquiries, and inquiries from integrated portals like Zillow or Realtor.com
- Team Collaboration — Programmatically add internal team notes to lead profiles and manage follow-up tasks to ensure no opportunity falls through the cracks
- Deal & Appointment Oversight — Monitor real estate transactions, commissions, and upcoming property showings directly through your agent
- System Automation — List and manage configured webhooks and account settings to maintain high-fidelity synchronization with your other tools
The Follow Up Boss MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 Follow Up Boss tools available for Cursor
When Cursor connects to Follow Up Boss through Vinkius, your AI agent gets direct access to every tool listed below — spanning lead-routing, real-estate-crm, follow-up-automation, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Add a note to a lead profile
Create a new task
Requires essential details like email or name. Add a new lead to the CRM
Get details for a specific lead
List showings and appointments
List active webhooks
List CRM tasks
List lead profiles (people)
List notes for a specific person
List transactions and deals
List website and activity events
Log a new activity event
Connect Follow Up Boss to Cursor via MCP
Follow these steps to wire Follow Up Boss into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Follow Up Boss
Why Use Cursor with the Follow Up Boss MCP Server
Cursor AI Code Editor provides unique advantages when paired with Follow Up Boss through the Model Context Protocol.
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
Follow Up Boss + Cursor Use Cases
Practical scenarios where Cursor combined with the Follow Up Boss MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Follow Up Boss in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Follow Up Boss immediately.
"List all my new leads from the last 24 hours."
"Add an internal note to lead 'p_123': 'Interested in 3-bedroom houses in North London'."
"Show me my upcoming property showings for today."
Troubleshooting Follow Up Boss MCP Server with Cursor
Common issues when connecting Follow Up Boss to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Follow Up Boss + Cursor FAQ
Common questions about integrating Follow Up Boss MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.