
Famulor
io.famulorPublished by famulor.ioOfficial publisherv1.0.0Updated Nov 2, 2026
Manage AI assistants, history, calls, campaigns, contacts, knowledge, messaging, and automations.
Overview
Remote MCP server for the Famulor platform, letting an assistant manage AI voice assistants, calls, campaigns, contacts, knowledge bases and messaging.
- What you can do
- Create, update and delete AI voice assistants; list voices, languages, models and TTS/STT providers
- Inspect cross-channel history and transcripts, and make and manage calls
- Create and run campaigns with retry rules and allowed-hours windows
- Manage contacts, tags, segments, suppression and campaign membership
- Create and maintain knowledge bases, including website-scraped documents
- Handle telephony, messaging and email channels, plus automations, webhooks and workspace settings
- When to use it
- Useful when you work in Famulor and want an assistant to build or adjust voice agents, launch and monitor campaigns, review call transcripts, or send WhatsApp and other channel messages from plain-language requests.
- Requirements
- A remote endpoint at app.famulor.io/mcp; nothing to install or host. OAuth sign-in in the browser with a workspace and permission approval is required. Server-to-server clients can use an API key as an Authorization Bearer token. The Famulor plan must include the Connect AI / MCP feature, otherwise the endpoint returns 403.
Installation
In SourceWeft
- Open Famulor in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.famulor%2Ffamulor-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"famulor": {
"type": "http",
"url": "https://app.famulor.io/mcp"
}
}
}README
Famulor MCP
Connect Claude, Codex, Cursor, VS Code, and other MCP clients to the complete tenant-safe Famulor platform API.
MCP endpoint · API & MCP settings · Docs
[GitHub] [Famulor] [MCP] [MIT]
Setup
Add the server in your client, then sign in to Famulor and approve the requested workspace permissions in the browser. Claude and ChatGPT use OAuth; there is no API key to paste into their connector settings.
Server URL:
https://app.famulor.io/mcp. It runs inside the Famulor platform, so there is nothing to install or host. Your plan needs the Connect AI / MCP feature; without it the endpoint answers403.
Claude Code
Add the server first, then complete the browser-based OAuth flow.
Claude Desktop
Settings > Connectors > Add custom connector
Copy the URL, paste it into the connector dialog, and sign in when prompted.
Cursor
.cursor/mcp.json
Add the server first, then complete the browser-based OAuth flow.
Windsurf
~/.codeium/windsurf/mcp_config.json
Add the server first, then complete the browser-based OAuth flow.
VS Code
.vscode/mcp.json
Add the server first, then complete the browser-based OAuth flow.
Cline
Cline extension > MCP Servers > Configure
Add the server first, then complete the browser-based OAuth flow.
Continue
~/.continue/config.yaml
Add the server first, then complete the browser-based OAuth flow.
OpenClaw
Or in ~/.openclaw/openclaw.json:
Tip: there is also a ready-made Famulor skill — openclaw skills install famulor-skill.
Hermes Agent
Or in ~/.hermes/config.yaml:
Apply in-session with /reload-mcp.
Zed
~/.config/zed/settings.json
Add the server first, then complete the browser-based OAuth flow.
What you can do
Once connected, your AI assistant discovers the current public tool catalog directly from Famulor. The catalog covers, among other areas:
Assistants — create, update, delete AI voice agents · list voices, languages, LLM/multimodal models, TTS/STT providers · toggle inbound and conversation-ended webhooks
History & calls — inspect cross-channel history and transcripts · make and manage calls
Campaigns — create campaigns, manage retry rules and allowed-hours windows · start, stop and delete
Audience — manage contacts, tags, segments, suppression and campaign membership
Knowledge bases — create knowledge bases · upload website-scraped documents · update / delete
Telephony — phone numbers, number verification, assignments and SIP trunks
Messaging & email — WhatsApp, Instagram, Messenger, Telegram, Slack, Teams, Discord, Google Chat, X, helpdesk and email conversation workflows
WhatsApp — list senders and templates · check 24h session window · send template or freeform messages
Automations & operations — flows, routines, dashboards, integrations, webhooks, booking, workspace settings and account administration
Ask the assistant in plain English, e.g. "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."
How auth works
The endpoint implements MCP OAuth discovery, authorization code with PKCE, dynamic client registration and Client ID Metadata Documents. Your MCP client opens Famulor in a browser, where you sign in on app.famulor.io, choose a workspace and approve the requested permissions.
Server-to-server clients can send an API key instead: create one under
Settings > API & MCP on app.famulor.io and pass it as
Authorization: Bearer fam_…. Claude and ChatGPT connectors always use OAuth.
Full tool catalog and scopes: docs.famulor.io/mcp/tools-and-scopes
Famulor 1.0 (app.famulor.de)
This MCP server works with workspaces on the Famulor platform at app.famulor.io. Famulor 1.0 (app.famulor.de) stays available; to bring assistants, tools, knowledge, campaigns, automations and your own telephony over, use Migrate from Famulor 1.0.
What is in this repository
The server itself runs inside the Famulor platform. This repository holds what clients and directories need to find it:
The earlier self-hosted server and its npm package famulor-mcp are retired.
License
MIT
Source: README.md at commit d61aaa8
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.