Famulor MCP Server

Control your Famulor AI voice agents — calls, leads, campaigns, knowledge bases, conversations, WhatsApp, SIP trunks — directly from ChatGPT, Claude, Cursor, Windsurf, VS Code, and any other MCP-compatible client.

Connect a client

Setup for ChatGPT, Claude, Cursor, and more

Hosted server

app.famulor.io/mcp — no install required

GitHub

Source code and deployment

Overview

The full Famulor MCP endpoint exposes a broad platform tool catalog for developer clients. Ask in plain language — the model chooses the right tools. All tools return structured output and carry title annotations for directory-compatible clients. Example prompts:

“Create a German sales assistant using GPT-4.1-mini and the Susi voice”
“Start campaign #42 and add these 50 leads”
“Show me all calls today where the goal wasn’t reached”
“Create a ‘Clients’ folder and move all inbound assistants into it”

Need inspiration? See Use Cases & Prompts — grouped scenarios with ready-to-use prompts and best practices.

New to MCP? Start with MCP Client setup — add the server URL, then sign in to Famulor through OAuth in the browser.

Hosted endpoints

Endpoint	URL
MCP (canonical)	`https://app.famulor.io/mcp`
Assistant & History (read-only)	`https://app.famulor.io/mcp?profile=assistant-history`
Base URL	`https://app.famulor.io/mcp`
Health	https://app.famulor.io/health
OAuth metadata	`https://app.famulor.io/.well-known/oauth-authorization-server`

Use the restricted Assistant & History URL for ChatGPT and Claude directory or consumer-facing connectors. Use the canonical endpoint for developer clients that intentionally need the full catalog.

What you can do

Area	Capabilities
Assistants	Create, update, delete AI voice agents · list voices, languages, LLM/multimodal models, TTS/STT providers · toggle inbound and conversation-ended webhooks · organize via `folder_id` / `label_ids`
Folders & Labels	Organize assistants into folders (one folder per assistant) · tag with colored labels (multiple per assistant) · create, rename, delete
Calls	Make outbound calls · list / get / delete call records
Campaigns	Call, WhatsApp & SMS campaigns · schedule windows · get/list/create · start, stop, delete · call→text fallback
Leads	Add leads (incl. secondary contacts) · update status and merge variables · delete
Knowledge bases	Create knowledge bases · upload website-scraped documents · update / delete
Phone numbers	Search by country and dial pattern · purchase · set nickname (`update_phone_number`) · release · SIP trunk CRUD
Conversations	List, read, reply to chats · enable/disable AI per conversation (human takeover)
WhatsApp	List senders and templates · check 24h session window · send template or freeform messages
SMS	Send via your purchased numbers
Mid-call tools	Register custom HTTP integrations the assistant can call mid-conversation
AI Replies	Generate context-aware replies for external chat platforms

Authentication

The server uses MCP OAuth 2.1 (RFC 8414 metadata, RFC 7591 Dynamic Client Registration, PKCE S256):

Your MCP client opens a browser tab.
You sign in to your normal Famulor account and review the requested permissions.
After approval, the client receives a scoped access token.

The hosted OAuth flow does not ask you to paste an API key. The Assistant & History profile requests only assistants:read and calls:read.

Supported clients

ChatGPT — custom app with OAuth (setup guide)
Claude — Desktop connector and Claude Code CLI (setup guide)
Cursor, Windsurf, VS Code, Cline, Continue, Zed

See MCP Client for step-by-step instructions per client.

Demo video

Self-hosting

The hosted server at https://app.famulor.io/mcp works out of the box. To run your own instance:

Run locally via npm (stdio)

The server is published to npm as famulor-mcp. Run it as a local stdio MCP server — no hosting, no OAuth:

npx -y famulor-mcp          # or: npm i -g famulor-mcp && famulor-mcp

Point a client at it with a stdio config, passing your API key as an env var:

{
  "mcpServers": {
    "famulor": {
      "command": "npx",
      "args": ["-y", "famulor-mcp"],
      "env": { "FAMULOR_API_KEY": "your-api-key" }
    }
  }
}

For most setups the hosted server (https://app.famulor.io/mcp with OAuth sign-in) is simpler — use the npm package when you need a local, offline, or embedded stdio server.

Deploy to Vercel

git clone https://github.com/bekservice/Famulor-MCP.git
cd Famulor-MCP
vercel --prod

Set these environment variables in the Vercel project:

Variable	Required	Value
`MCP_SECRET`	yes	`openssl rand -hex 32` — encrypts OAuth tokens
`MCP_ISSUER`	recommended	Your public URL, e.g. `https://mcp.example.com`

Point your domain at the deployment. See the DEPLOYMENT.md guide in the repository for stdio mode and full details.

Local development

npm install
echo "MCP_SECRET=$(openssl rand -hex 32)" > .env
npm run dev:http
# server on http://localhost:8787

curl http://localhost:8787/health
curl http://localhost:8787/.well-known/oauth-authorization-server

About MCP

Model Context Protocol (MCP) lets AI assistants securely connect to external tools and data. The Famulor MCP server maps platform APIs to MCP tools after you authenticate with your Famulor account through OAuth.

Resources

License

See the current repository license for the self-hosted package terms.

Related pages: Use Cases & Prompts, MCP Client, Famulor Skill.

​Famulor MCP Server

Connect a client

Hosted server

GitHub

​Overview

​Hosted endpoints

​What you can do

​Authentication

​Supported clients

​Demo video

​Self-hosting

​Run locally via npm (stdio)

​Deploy to Vercel

​Local development

​About MCP

​Resources

​License

Famulor MCP Server

Overview

Hosted endpoints

What you can do

Authentication

Supported clients

Demo video

Self-hosting

Run locally via npm (stdio)

Deploy to Vercel

Local development

About MCP

Resources

License