Tools and scopes

Once a client is connected (see Connect an AI client), plain language reaches every tool it’s approved for. This page covers the full catalog, how to narrow it, and what happens with long-running or failed operations.

Tool groups

The complete catalog is organized into 13 groups. A workspace API key connection gets the full catalog by default; an OAuth connection (Claude, ChatGPT) gets a curated subset of 7 by default — see What a connected client can see.

Group	Customer-facing capabilities
`assistants`	Assistants, versions, models, voices, reusable tools, bookings, and simulations
`calls`	Calls, conversation history, transcripts, and permitted call actions
`campaigns`	Campaigns, audiences, leads, suppression, and CRM sync
`messaging`	Messaging and email connectors, templates, and conversations
`telephony`	Phone numbers, SIP trunks, your own carrier connections and BYOC import, caller-ID and number verification, and the full Famulor Loop system — presence, ring groups, queues, routing rules, devices, and Recall
`knowledge`	Knowledge bases, documents, website imports, and connected file sources
`dashboards`	Analytics dashboards and widgets
`automations`	Automations, connections, Milian Missions, and run history
`billing`	Balance, usage, transactions, referrals, and outbound limits
`settings`	Workspace settings, domains, API keys, and retention
`platform`	White-label customer management for authorised resellers
`migration`	Preview and import Famulor 1.0 resources or inactive assistant shells from Retell AI, Vapi, and Synthflow
`tasks`	Long-running exports, crawls, simulations, and campaign preparation

The MCP client receives the current input schema, permissions, and safety hints for every tool it is allowed to use. This live discovery is the authoritative reference for individual tool arguments.

Choosing which tools to expose

Select one or more groups when connecting:

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

You can also send X-MCP-Toolsets: assistants,calls. The header takes precedence over the query parameter. Use list_mcp_toolsets to see the groups available to your account — it’s always available regardless of which groups you’ve selected. For a workspace API key connection, add ?toolsets=all to get the complete 13-group catalog instead of the default curated set.

Public directory profile

The reviewed ChatGPT and Claude directory connection uses:

https://app.famulor.io/mcp?profile=assistant-history

This profile is limited to read-only assistant information and read-only conversation history. It excludes assistant changes, outbound calls, campaigns, messaging, phone-number management, billing, integrations, and tool-group discovery. Custom MCP connections keep the permissions selected during their own setup.

Long-running tasks

Website imports, simulations, history exports, and large campaign preparations may continue as MCP tasks. A compatible client can show progress, retrieve the result, or request cancellation. Cancellation stops remaining work when possible; an action already accepted by an external service may still complete. Exports use short-lived private download links. Tasks and their results remain limited to the workspace and credential that created them. Call-history tools return a provider-neutral failure object when a call cannot complete. Use its code, customer-safe message, retry guidance, and suggested action instead of relying on infrastructure-specific details.

Errors

Status	Meaning
`401`	The token is missing or invalid; reconnect the client
`403`	The plan, role, or approved scopes do not allow the requested action
`405`	Send MCP requests with `POST`
`429`	Too many requests; wait and retry — see Rate limits

​Tool groups

​Choosing which tools to expose

​Public directory profile

​Long-running tasks

​Errors

Tool groups

Choosing which tools to expose

Public directory profile

Long-running tasks

Errors