Bring Lead Routing
to CrewAI
Learn how to connect Follow Up Boss 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.
What is the 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.
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
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Follow Up Boss admin settings (Admin > API)
3. Start managing your real estate business from Claude, Cursor, or any MCP client
No more manual status checking or digging through CRM lists on the go. Your AI acts as your dedicated real estate operations assistant.
Who is this for?
- Real Estate Agents — instantly retrieve lead details and log field activity using natural language commands
- Team Leaders — monitor team-wide lead engagement and pipeline health without opening the web dashboard
- Inside Sales Agents (ISAs) — automate lead triaging and task management through simple AI queries
Built-in capabilities (12)
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
Why CrewAI?
When paired with CrewAI, Follow Up Boss becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Follow Up Boss 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
Follow Up Boss in CrewAI
Follow Up Boss and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Follow Up Boss 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 Follow Up Boss in CrewAI
The Follow Up Boss 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
Follow Up Boss for CrewAI
Every tool call from CrewAI to the Follow Up Boss 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 API Key in Follow Up Boss?
Log in as an Admin, navigate to Admin > API, and click Create API Key to generate your unique token.
Can I filter leads by their recent activity?
Yes! Use the list_recent_events tool to see who has registered or inquired lately across all your integrated channels.
How do I get a specific person's ID?
Use the list_leads tool to retrieve your contact list. Each result includes a unique id which you can use for granular details or notes.
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.