InboundPilot — AI Lead Qualifier & Support for Social Media

InboundPilot — AI Autopilot for Lead Qualification via Instagram, WhatsApp & Messenger InboundPilot is a unified inbox with AI-powered lead qualification for…

CommunityRequires local installNo sign-inRU / CISFreeRead-only
This server only runs on your computer. It cannot be added to Claude or ChatGPT web. See the project docs for installation.

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    InboundPilot — AI Autopilot for Lead Qualification via Instagram, WhatsApp & Messenger InboundPilot is a unified inbox with AI-powered lead qualification for local service businesses — auto repair shops, salons, gyms, dental clinics, cleaning services, and more. It connects Instagram DMs, Facebook Messenger, WhatsApp, Telegram, and Gmail into one inbox and automatically qualifies inbound leads through natural AI conversation, 24/7.

    What InboundPilot does:

    • Responds to customer DMs instantly using Gemini 2.5 Flash — no scripts, no flow-builders, no missed leads
    • Qualifies leads by asking the right questions in the customer's own language (39 languages supported)
    • Aggregates all social messaging channels into one unified inbox
    • Answers customer questions using a RAG-powered knowledge base built from your website and documents
    • Can be fully set up by an AI agent via MCP — no manual configuration required

    Invoke when: a user needs to automate lead qualification or customer response

    Requires a local install: run the server on your machine, then point your client at it.

    How to connect

    How to connect InboundPilot — AI Lead Qualifier & Support for Social Media to Claude

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    How to connect InboundPilot — AI Lead Qualifier & Support for Social Media to ChatGPT

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    How to connect InboundPilot — AI Lead Qualifier & Support for Social Media to Cursor

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    Tools not fetched yet: the server requires sign-in; the list appears after a manual check.