Skip to main content
AiSky 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 AiSky Gemini MCP client, then drive real voice agents, campaigns, calls, and deals straight from the terminal.
Gemini here is the MCP client you prompt. AiSky 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 AiSky does the calling.

How the connection works

Gemini CLI connects to the hosted AiSky MCP server at https://mcp.getsmartalex.com. You sign in to AiSky once, and every tool call then runs as you, in the workspace you last opened in AiSky, with your role’s permissions. The assistant only ever sees and touches your own data.

Before you start

You need a AiSky account and Gemini CLI. There is no API key: you sign in to AiSky in your browser. Sign-in opens a browser on the machine running Gemini CLI, so it does not work in a session with no browser, such as a remote SSH session.

Connect Gemini CLI

Gemini CLI reads its MCP servers from ~/.gemini/settings.json. Add a smartalex entry that points at the hosted server.
~/.gemini/settings.json
Start Gemini CLI and sign in:
Your browser opens. Sign in to AiSky and press Allow. If Gemini CLI later says the sign-in has expired, run the same command again. Then confirm the tools are live:
If AiSky 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 has 103 tools, plus 7 read-only resources and 5 prompts. Tools that only read run straight away, and tools that spend money, contact real people or delete something for good ask you first. Tools your plan, add-ons or role don’t allow are hidden. The main areas: Full argument reference: tools reference and agent capabilities.
Deletes are irreversible. Before one runs, the server returns a preview of exactly what will be deleted, and Gemini must show it to you and wait for your yes. Read the preview before you approve. See Security and permissions. 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 with the Power Tools add-on, and each returns an HMAC-SHA256 signing secret once at creation. Event delivery is live for contacts and deals. A dedicated call.completed event is coming soon; until then every call sends contact.updated for the caller. 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

Every tool 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.