Bring Lead Routing
to LangChain
Learn how to connect Follow Up Boss to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Follow Up Boss through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Follow Up Boss MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Follow Up Boss queries for multi-turn workflows
Follow Up Boss in LangChain
Follow Up Boss and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Follow Up Boss to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters