Skip to main content
SmartAlex ships a live Model Context Protocol (MCP) server, so any MCP-capable client can operate your workspace just by talking to it. This page shows how to wire up Gemini CLI as a SmartAlex Gemini MCP client, then drive real voice agents, campaigns, calls, and deals straight from the terminal.
Gemini here is the MCP client you prompt. SmartAlex runs the actual voice agents that place and answer calls. Our voice layer is curated, high-accuracy speech, language, and voice models, kept abstracted. So if you searched for “Gemini voice AI,” the honest picture is simple: you talk to Gemini, and SmartAlex does the calling.

How the connection works

Gemini CLI speaks to the SmartAlex MCP server over stdio. Every tool call runs against your workspace, scoped to your API key, so the assistant only ever sees and touches your own data.

Before you start

1

Add the Power Tools add-on

MCP API keys are gated behind the Power Tools add-on ($29/month on Professional, included on Enterprise). See add-ons or pricing.
2

Have a super-admin role

Only a super-admin on the workspace can mint keys in the Developer Portal (the side nav in your dashboard).
3

Create an API key

Generate a key in the Developer Portal. Production keys start with sa_live_, test keys with sa_test_. The full key is shown once at creation (only a hash is stored), so copy it immediately. Lose it and you regenerate, you never recover it.

Connect Gemini CLI

Gemini CLI reads its MCP servers from ~/.gemini/settings.json. Add a smartalex entry that launches the SmartAlex MCP server locally over stdio, passing your key through the environment.
On Windows, wrap the launcher in cmd: set "command": "cmd" and "args": ["/c", "npx", "-y", "@smartalex/mcp-server"].
Restart Gemini CLI so it picks up the new server, then confirm the tools are live:
If SmartAlex responds with your agents, the connection is good. Every tool is prefixed smartalex_, so it is easy to spot which calls are hitting the platform.

Example prompts

Once connected, you operate the account conversationally. Gemini interprets intent, then calls the right smartalex_ tools in sequence.
That last one returns the exact script tag you drop onto any site:

What the server exposes

The MCP server surfaces 28 tools, 7 read-only resources, and 5 prompts across 8 domains. 14 tools read, 14 write, and 3 are destructive (smartalex_delete_agent, smartalex_delete_deal, smartalex_delete_webhook). Full argument reference: tools reference and agent capabilities.
Deletes are irreversible. When a prompt could trigger smartalex_delete_*, ask Gemini to confirm the exact record first. Requests are rate limited to 100 per minute per workspace, so batch large jobs rather than firing hundreds of single calls.
Webhook subscriptions are creatable through MCP today, and each returns an HMAC-SHA256 signing secret once at creation. Outbound event delivery is still in private beta, so do not build hard dependencies on real-time event push yet. For live event-driven automation, use Custom HTTP Tools (Power Tools), which let an agent call your own HTTPS endpoint mid-call.

MCP getting started

Every supported client, transport, and config file in one place.

Tools reference

All 28 tools with arguments and return shapes.

Build with Claude Code

The cloud, OAuth-based connect flow for Claude Code.

What is MCP?

A plain-English primer on the Model Context Protocol.