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

Connect with the Famulor connector in Claude’s directory.
  1. Open the directory page and choose Connect.
  2. Sign in to your Famulor account and approve the requested access.
  3. Start a chat and ask, for example: “Review my support assistant and summarize its recent calls.”
The directory connector provides read-only assistant information and conversation history. See Public directory profile.
To create and change assistants, start campaigns, or use a white-label domain, add a custom connector with the URL shown in Settings → API & MCP:
  1. Customize → Connectors → + Add → 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 in the sidebar and Add to Claude in Settings → API & MCP offer both options: the directory connector or a prefilled custom connector.

​
Connect from inside Famulor

Choose Connect in the sidebar or open Settings → API & MCP. Claude and ChatGPT both offer Custom connector, using your workspace’s plain MCP URL by default. Platform workspaces can also choose the marketplace connector, marked Limited, for read-only assistants and history. White-label customer workspaces use their own custom connection. Tool-group filtering is optional; the OAuth consent screen controls what you approve. Claude also offers starter tasks.
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.
API key creation form with an empty name field and Create key button

For your own server integration, open Settings → API & MCP → Create a new API key, enter a recognizable name and select Create key.

​
What a connected client can see

The official ChatGPT plugin uses the read-only public directory profile. Its permissions stay limited to assistant information and conversation history. Custom connections use /mcp by default. When you approve a new connection, all selected tool groups are saved, including an explicit selection of every group. Access still depends on the client’s requested permissions, your approved scopes, workspace role, and plan. A tool appearing in the catalog does not itself authorize an action. Existing connections keep their token permissions. To add missing access, revoke the old connection under Settings → API & MCP, reconnect, and approve the required groups. Refresh the tools or start a new chat in your AI client afterward. Toolsets remain useful as an optional filter for focused workflows or clients that struggle with a large catalog. URL and header filters cannot expand a token’s explicitly approved groups. Marketplace connections remain limited to their reviewed profile.

​
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.