Smitline

What Smitline does

The Smitline MCP server gives an AI agent access to a phone line and browser-based participation in online meetings. An agent can request a call to a restaurant, office, service provider, or individual, or ask Smitline to join a meeting link. During a call, it speaks in real time, identifies itself as an AI assistant, and follows the instructions supplied by the agent.

After the interaction, the requesting chat receives the result. Returned information can include the outcome, times, prices, confirmation numbers, decisions, action items, the full transcript, and the call cost. A local dashboard displays live call transcripts and lets a person take over a call from their phone.

How it works

The agent first creates a short brief describing the objective, information to gather, permitted commitments, and details that must remain private. Smitline uses that brief during the conversation and brings unexpected requests back to the user rather than agreeing to them automatically.

Phone conversations use OpenAI GPT-Live together with a SignalWire or Twilio account. Meetings are joined through a browser as a participant. Zoom has been tested live; Teams and Google Meet use the same runtime but have had less live testing.

Calls identify who they are calling for and why, disclose that they are an AI assistant, and answer honestly if asked. Built-in phone guardrails block emergency and premium-rate numbers, restrict calling to 8 AM–9 PM in the recipient’s time zone, honor requests to stop calling, and limit repeat calls.

Setup and configuration

Smitline runs as a self-hosted Docker container. Docker Desktop 4.34 or newer is required on Mac or Windows, with host networking enabled; Linux users can use Docker Engine. The setup page is opened locally at http://127.0.0.1:8095, where the required keys are entered instead of placing them in an agent chat.

An OpenAI API key with GPT-Live access and billing enabled is required. Phone calls additionally require a SignalWire account or a funded Twilio account. Meetings do not require a separate meeting provider account because Smitline joins through the browser as a guest.

Meeting support requires mounting the Docker socket so Smitline can start its meeting container. That mount gives the container control of Docker on the host, close to administrator access. Phone-only deployments can omit the socket mount. The container stores keys, call records, and transcripts on the local computer; audio is sent to OpenAI and the selected phone provider.

Tools and capabilities

The Smitline MCP server supports these agent-directed activities:

• Place phone calls using SignalWire or Twilio.
• Join Zoom, Microsoft Teams, and Google Meet meetings.
• Hold real-time conversations using a supplied brief.
• Follow limits on pricing, decisions, and private information.
• Return transcripts, outcomes, action items, decisions, and costs.
• Show a live transcript and allow a person to take over a call.

The project also states that agents can use Smitline through MCP, a CLI, or a REST API, and names Claude Code, Codex, Cursor, Claude Desktop, OpenClaw, and Hermes as supported agent environments.

Limitations and notes

Phone calls are described as being in daily use through SignalWire. Meeting support is more extensively tested with Zoom than with Teams or Google Meet. The first meeting may require about 1.8 GB of disk space, in addition to roughly 600 MB for the download. SignalWire trial accounts may restrict calls to verified numbers; adding a card and credit removes that stated trial limitation.

The project is licensed under Apache-2.0. Smitline is self-hosted rather than a hosted Smitline service, so deployment, provider credentials, Docker access, and local records remain under the operator’s control.