Skill

Manage voice agents, campaigns, and messaging workflows

Operate Famulor voice agents, campaigns, messaging channels, and telephony through authenticated MCP toolsets for assistants, calls, and automations.

Works with famulorwhatsappmessengerslacksip

80
Spark score
out of 100
Updated today
Version 1.0.0

Add to Favorites

Why it matters

Connect AI assistants to Famulor's voice, messaging, and campaign platform to configure assistants, run outbound campaigns, manage calls and transcripts, sync CRM data, and control telephony resources through authenticated workspace operations.

Outcomes

What it gets done

01

Configure voice assistants with models, voices, tools, and integrations

02

Launch and monitor outbound call or messaging campaigns with consent tracking

03

Retrieve call transcripts, history, and quality-assurance data

04

Manage phone numbers, SIP trunks, knowledge bases, and billing

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-famulor-skill | bash

Overview

Famulor

Famulor is a hosted Streamable HTTP MCP server that exposes 282 authenticated tools across 12 toolsets for managing workspace operations. It provides access to assistants, calls, campaigns, messaging (WhatsApp, Messenger, email, Slack), telephony (phone numbers, SIP trunks), knowledge bases, dashboards, automations, billing, settings, platform administration, and migration operations. Use Famulor when you need real workspace data or authenticated actions: configuring assistants and voices, managing call transcripts and history, running campaigns with consent tracking, operating multi-channel messaging, provisioning phone numbers, maintaining knowledge bases, syncing CRM automations, or reviewing billing. Do not use for generic voice-agent advice that does not require authenticated workspace operations.

What it does

Famulor is a hosted Streamable HTTP MCP server that provides authenticated access to workspace operations. It exposes 282 tools organized into 12 toolsets covering assistants, calls, campaigns, messaging, telephony, knowledge bases, dashboards, automations, billing, settings, platform administration, and migration. Authentication is handled via OAuth flow in the MCP client or a workspace API key for server-to-server scenarios, and the server enforces workspace-level tenant boundaries, scopes, roles, and plan entitlements.

When to use - and when NOT to

Use Famulor when a request requires real workspace data or authenticated actions: configuring assistants and their versions, managing call history and transcripts, running campaigns with audience contacts and consent tracking, operating WhatsApp/Messenger/email/Slack messaging, provisioning phone numbers and SIP trunks, maintaining knowledge bases with documents and FAQs, building dashboards, syncing CRM automations, reviewing billing and usage, or administering workspace settings and API keys.

Do NOT use Famulor for generic voice-agent advice that does not require authenticated workspace operations. Do not substitute undocumented REST endpoints if the MCP server is unavailable; instead, help the user connect the server first.

Inputs and outputs

Users provide the MCP endpoint URL with optional toolset filtering to narrow context:

https://app.famulor.io/mcp?toolsets=assistants,calls

Authentication happens via OAuth flow in the MCP client or a workspace API key for server-to-server scenarios. Users specify the workspace, requested outcome, and any required targets (assistant ID, campaign ID, phone number, etc.). The server provides live tool schemas, and available tools, fields, scopes, plan features, prices, limits, and provider behavior can differ by workspace and change over time.

Integrations

Famulor integrates with:

  • Assistants toolset (56 tools): assistant versions, models, voices, reusable tools, bookings, tests, and integrations
  • Calls toolset (15 tools): call records, unified history, transcripts, QA analysis, callbacks, and live call control
  • Campaigns toolset (34 tools): audience contacts, leads, segments, consent management, suppression lists, and outbound limits
  • Messaging toolset (44 tools): WhatsApp, Messenger, email, Slack connectors, templates, and sender profiles
  • Telephony toolset (27 tools): phone numbers, SIP trunks, caller IDs, carriers, and number verification
  • Knowledge toolset (20 tools): knowledge bases, documents, FAQs, website crawls, and connected drives
  • Dashboards toolset (19 tools): analytics dashboards, widgets, and layout configuration
  • Automations toolset (28 tools): workflow automations, CRM sync connections, routines, and execution runs
  • Billing toolset (7 tools): balance, usage tracking, transactions, invoices, billing recovery, and referrals
  • Settings toolset (20 tools): account administration, workspaces, API keys, retention policies, memory, domains, and sessions
  • Platform toolset (6 tools): white-label reseller customer administration
  • Migration toolset (2 tools): previewing and importing Famulor 1.0 resources
  • Tasks toolset (4 tools): durable exports, simulations, crawls, and campaign preparation

Who it's for

Famulor is designed for users who need to read and modify workspace state through authenticated operations. The workflow emphasizes reading current state before mutations, using preview and test tools when available, verifying results with corresponding read operations, and respecting workspace boundaries, OAuth scopes, plan entitlements, consent states, and compliance requirements. The server enforces that outbound calls, messages, campaign starts, live-call control, phone-number purchases, credit transfers, and destructive actions require explicit user authorization of the exact target and action.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.