3,400+ MCP servers ready to use
Vinkius

Follow Up Boss MCP Server for VS Code CopilotGive VS Code Copilot instant access to 12 tools to Add Internal Note, Create Followup Task, Create New Lead, and more

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this App Connector for VS Code Copilot

The Follow Up Boss app connector for VS Code Copilot 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

RecommendedModern Approach — Zero Configuration

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "follow-up-boss-alternative": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Follow Up Boss
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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.

GitHub Copilot Agent mode brings Follow Up Boss data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot

When VS Code Copilot 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_internal_note

Add a note to a lead profile

create_followup_task

Create a new task

create_new_lead

Requires essential details like email or name. Add a new lead to the CRM

get_lead_details

Get details for a specific lead

list_calendar_appointments

List showings and appointments

list_configured_webhooks

List active webhooks

list_followup_tasks

List CRM tasks

list_leads

List lead profiles (people)

list_person_notes

List notes for a specific person

list_real_estate_deals

List transactions and deals

list_recent_events

List website and activity events

log_lead_activity

Log a new activity event

Connect Follow Up Boss to VS Code Copilot via MCP

Follow these steps to wire Follow Up Boss into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Follow Up Boss

Ask Copilot: "Using Follow Up Boss, help me...". 12 tools available

Why Use VS Code Copilot with the Follow Up Boss MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Follow Up Boss through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Follow Up Boss + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Follow Up Boss MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Follow Up Boss in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Follow Up Boss immediately.

01

"List all my new leads from the last 24 hours."

02

"Add an internal note to lead 'p_123': 'Interested in 3-bedroom houses in North London'."

03

"Show me my upcoming property showings for today."

Troubleshooting Follow Up Boss MCP Server with VS Code Copilot

Common issues when connecting Follow Up Boss to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Follow Up Boss + VS Code Copilot FAQ

Common questions about integrating Follow Up Boss MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.