Every API operation is a command.
Commands are generated from the OpenAPI spec. Type the operation name, or an area plus a verb.
Assistants
assistantsCalls
callsCampaigns and leads
campaignsPhone numbers
phone-numbersKnowledge bases
knowledge-basesAnything else
famulor apiEvery area lists its commands: famulor <area>
- assistants
- calls
- campaigns
- leads
- phone-numbers
- voices
- knowledge-bases
- tools
- automations
- bookings
- messaging
- sms
- history
- integrations
- widgets
- translation
- loop
- milian
- qa
- dashboards
- segments
- callbacks
- suppression
- caller-ids
- sip-trunks
- carrier-connections
- white-label
- workspaces
- api-keys
- billing
- settings
- account
- catalog
- migrations
Readable for you. Parsable for scripts.
One response, three formats. Add --all and the CLI fetches every page of a list.
Your coding agent knows every command.
Agents read every command schema as JSON and get errors back in a form they can parse. Colors, animation and prompts switch off on their own.
Find commands
famulor commands recordingRead the schema
famulor create-call --help --output jsonErrors as JSON
{"error":{"code","message","status","exit_code"}}Works in any agent that runs shell commands
Claude Code
Codex
Cursor
Gemini CLI
Windsurf
Warp
OpenClaw
Hermes
You: Call +49 30 123456 with Front Desk.
Agent: Done. The call is started, status: queued.
Nothing happens by accident.
A question before every delete, a preview of every request and a key that never sits in plain text.
Asks before it deletes
Deletes and irreversible actions like buying a number ask first. In scripts you confirm with --yes.
Preview with --dry-run
You see the method, URL, headers and body. The key is redacted and nothing is sent.
No call placed twice
Requests that create something are never retried after a timeout. Rate limits are waited out for you.
Key in the keychain
The key is checked before it is saved, then kept in the macOS, Windows or Linux keychain.
One profile per workspace
Save one login per workspace and switch with famulor auth switch. In CI, FAMULOR_API_KEY is enough.
On your own domain too
White-label partners log in once with --base-url. The profile remembers the host.
Three ways in. Pick the one that fits.
All three work on the same workspace and the same data.
Famulor CLI
For terminals, scripts, CI and coding agents.
- One command per API operation
- JSON, table or JSONL
- Key in your OS keychain
MCP Connector
For Claude, ChatGPT and other AI tools in chat.
- One server URL, OAuth sign-in
- Famulor tools right in the chat
- Nothing to install locally
REST API
For your own product and backend.
- OpenAPI specification
- Real-time webhooks
- Any language, any framework
One tool for the whole platform.
Command per operation
1:1
Generated from the OpenAPI spec.
Output formats
3
JSON, table and JSON Lines.
Clear exit codes
0–5
Success, API, usage, login, not found, cancelled.
Shell completions
3
bash, zsh and fish.
Ready in three commands.
Install, log in, go.
- 01
Install
npm install -g famulor. Runs on macOS, Linux and Windows with Node.js 22 or newer.
- 02
Log in
famulor login asks for your API key from Settings → API & MCP and checks it before saving it.
- 03
Go
famulor --help shows every area. famulor calls, for example, lists every command for calls.
More from the platform
Other building blocks teams usually pair with this one.
Questions before you go live
What is the Famulor CLI?
The Famulor CLI is the official command-line tool for Famulor. Every public REST API operation is a command: assistants, calls, campaigns, leads, phone numbers, knowledge bases, automations and more. Use it in your terminal, in scripts, in CI or through your coding agent.
What do I need to use the CLI?
Node.js 22 or newer and a workspace plan with API Access. Install it with npm install -g famulor. Create an API key in the dashboard under Settings → API & MCP, then run famulor login.
Where is my API key stored?
famulor login checks the key against the API before anything is saved. It then goes into your system keychain: macOS Keychain, Windows Credential Manager or Linux Secret Service. Without a keychain it is saved to a file only you can read. In CI, set FAMULOR_API_KEY instead.
Can I use the CLI with Claude Code, Codex or Cursor?
Yes. famulor commands <topic> returns matching commands as compact JSON, and famulor <command> --help --output json gives the full schema. Colors, animation and prompts switch off in agents and CI. On failure stdout stays empty and the last stderr line is the error as JSON, with a clear exit code.
When should I use the CLI, MCP Connector or API?
The CLI fits terminals, scripts, CI and coding agents. The MCP Connector brings Famulor into chat tools like Claude or ChatGPT with nothing to install. Use the REST API when you build Famulor into your own product. All three work on the same workspace.
Can I delete something by accident?
Deletes and irreversible actions such as buying numbers, transfers or restores ask for confirmation in a terminal. In scripts, CI and coding agents they only run with --yes. With --dry-run you see the exact request and nothing is sent.
Does it work with several workspaces and white-label?
Yes. An API key belongs to exactly one workspace. Save one profile per workspace with famulor auth login --profile <name> and switch with famulor auth switch. If you run Famulor on your own domain, log in once with --base-url.
Is the CLI stable yet?
The CLI is a public preview (version 0.x). Command names follow the API and may still change before 1.0. A renamed command keeps working for at least one minor version.
Your workspace, one command away.
Get an API key, install the CLI and start with famulor login.
The Famulor CLI is free and MIT licensed. It needs Node.js 22 or newer and a plan with API Access.