Skip to main content
The Model Context Protocol (MCP) endpoint lets an AI application work with the same workspace resources you use in the dashboard — assistants, calls, campaigns, knowledge bases, and more — subject to your plan, role, and approved permissions.
On a white-label domain, use that domain instead. The login and consent screens use the same branding. Your plan must include Connect AI / MCP.
This page covers connecting an AI client (Claude, ChatGPT, and others) to Famulor. Looking to connect one of your assistants out to an external MCP server mid-call — your own CRM or internal tools? See Tools & webhooks instead.

​
Connecting clients

  1. Open Settings → Connectors → Add custom connector.
  2. Enter https://app.famulor.io/mcp.
  3. Sign in and approve the requested permissions.
  4. The approved tools appear in Claude.

​
Connect from inside Famulor

Choose Connect in the sidebar, or Use with ChatGPT & Claude on the dashboard. The dialog shows the correct MCP URL for your current domain, lets you pick which tool groups to connect with (see Tools and scopes), and offers starter prompts for common tasks — build an assistant, diagnose one that misbehaves, analyze your last call, improve from your last 30 calls, or launch a campaign. The same picker is available any time from Settings → API & MCP.
Working from a coding agent such as Claude Code, Cursor, or Codex, install the open-source Famulor Skill with npx skills add bekservice/Famulor-Skill. It carries the endpoint configuration (add the URL manually if your client doesn’t pick it up) plus Famulor-specific working rules on top of raw MCP access: read current state before changing it, confirm anything hard to reverse, and stay inside the authenticated workspace.
Compatible clients start the OAuth sign-in automatically. The consent screen shows the requested tool groups before anything is shared, and your choice is remembered for future connections. Approved connections are listed under Settings → API & MCP, where each one can be revoked at any time. For a manual or server-to-server connection, send a workspace API key instead:
Use the narrowest scopes required. Write scopes include the corresponding read access.

​
What a connected client can see

By default, an OAuth-connected client (Claude, ChatGPT, and similar) gets a curated set of 7 tool groups — assistants, calls, campaigns, knowledge, telephony, billing, and settings — rather than the full catalog. This is a deliberate limit, not a plan restriction: Famulor’s complete tool catalog is large, and loading all of it at once is more than these clients reliably support. Selecting every group during setup still lands you on the curated set for this reason. To use fewer groups, deselect the ones you don’t need when connecting, or edit your selection any time under Settings → API & MCP. See Tools and scopes for what each group covers. If your integration genuinely needs the complete catalog — all 13 groups — connect with a workspace API key instead of OAuth, and add ?toolsets=all to the endpoint URL. This path is meant for your own scripts and server-to-server integrations, not for a general-purpose AI client.

​
Rate limits

MCP requests are rate-limited to keep the platform responsive for every workspace: A client that exceeds these limits receives a 429 response and should back off before retrying — see Errors.
The same customer capabilities are available through the REST API. Choose the interface that best fits your integration.