The MCP server and Custom HTTP Tools are the live programmatic surfaces today. A public REST API and TypeScript SDK are in private beta and coming soon.
At a glance
Bottom line: SmartAlex is one of the few voice platforms an AI agent can run end to end today, through a live MCP server with API-key or OAuth authentication, strict per-workspace isolation, and clear read and write scopes, with a public REST API arriving soon.
The operating surface
Every tool is prefixedsmartalex_ so it never clashes with other MCP servers, and each one maps to a real operation in your workspace. Grouped by domain, here is the full capability surface an AI agent gets.
Create and manage voice agents
An agent can stand up a working voice assistant from almost nothing. Give it a website URL andsmartalex_create_agent scrapes the business, analyzes it, generates an optimized prompt, and deploys a live agent in about 30 to 60 seconds. It can also set the assistant name, objective, first message, voice, and accent. From there it can list agents, read full configuration, update behavior and tools, assign a phone number, toggle active status, and delete an agent. Prompt-affecting changes regenerate the system prompt and sync automatically to the live voice platform.
Run outbound campaigns
The full outbound loop is available without a dashboard. An agent can create a campaign, set the objective and calling hours with a timezone, add contacts in batches, and start calling. It can read campaign detail including contact counts and call statistics, and check status as calls progress. Before starting, the tools guide the assistant to confirm the campaign has an agent, an objective, contacts, and a phone number, so it fails with a clear message rather than a bad run.Manage contacts and deals
An agent can keep your CRM current: list and look up contacts, create new ones with company and tags, and apply partial updates. On the pipeline side it can list deals filtered by stage, create deals with a value and linked contact, move them through stages fromlead to closed_won, and delete them. This lets an assistant turn a call outcome into a pipeline update in the same conversation.
Read calls and analytics
An agent can browse call history with direction, status, duration, sentiment score, and cost, then pull the full transcript for any single call. The platform status tool returns workspace usage stats (total contacts, campaigns, calls, and deals) alongside a health check, so an assistant can answer “how did last week look” from real data.Manage phone numbers
An agent can list the active numbers on the account, search available numbers by country across the supported regions, and buy a specific number in E.164 format. Purchased numbers are immediately usable for campaigns and agent assignment.Fetch widget install code
An agent can callsmartalex_get_widget_install_code to return a ready-to-paste HTML script tag plus platform-specific variants for React, WordPress, and Shopify, with a short install guide. This lets an assistant help a user embed the SmartAlex chat and voice widget on their site without leaving the conversation.
Set up webhooks
An agent can create event-driven integrations: subscribe an HTTPS endpoint to events such ascall.completed, deal.stage_changed, contact.created, and campaign.completed, list active subscriptions with their failure counts, and remove a webhook. Each subscription returns an HMAC-SHA256 signing secret once at creation for verifying delivery authenticity.
Beyond the tools, the server ships 7 read-only resources that give an assistant ambient context about your workspace, and 5 prompts that are ready-made workflows for campaign strategy, lead qualification, and call analysis.
Read versus write
Of the 28 tools, half read and half write, which makes it straightforward to grant an AI agent exactly the reach you intend.
Every tool carries MCP annotations so a well-behaved client knows how to treat it:
readOnlyHint marks the safe list and get tools, destructiveHint marks the three permanent deletes so cautious clients confirm first, and idempotentHint marks updates that are safe to retry. A key scoped to read that tries to call a write tool is rejected with a 403, so you can hand a reporting assistant read-only access with confidence.
The operating contract
An AI agent operates SmartAlex under a clear contract: how it authenticates, what it can reach, and how fast it can go.Authentication
The cloud server accepts a SmartAlex API key or an OAuth 2.0 token on theAuthorization: Bearer header. API keys suit local and scripted clients, while OAuth suits hosted clients that connect by URL and approve in the browser.
Keys are generated in the Developer Portal, which requires the Power Tools add-on and a super-admin role on the workspace. A key is shown once at creation; only a hash is stored, so a lost key is regenerated rather than looked up.
Tenant isolation
This is the guarantee that makes it safe to let an assistant act. Every credential resolves to exactly one workspace. An API key belongs to the workspace it was created in, and an OAuth token resolves to the user’s active workspace. The gateway then scopes every read and write to that workspace, so one credential can never reach another tenant’s data. An AI agent connected to your workspace only ever sees and touches your workspace.Rate limits
Going over returns a
429 with a Retry-After header and X-RateLimit-* headers, and most clients back off automatically. The public REST path, when it ships, will carry its own per-key limit (default 60 per minute, adjustable at key creation).
What stays hidden
Provider details are never exposed. Agent records returnvoice_provider as "cloud" rather than any underlying vendor, because SmartAlex runs a curated, high-accuracy speech-to-text, language, and text-to-speech stack behind the platform, and keeps it abstracted. Signing secrets and API keys are returned only once, and all traffic is HTTPS.
Live today, and what is next
Live now
The MCP server (cloud and local) and Custom HTTP Tools, which let an agent call your own HTTPS endpoint mid-call, are live in production today.
Coming soon
A public REST API, a TypeScript SDK, and outbound webhook events are in private beta. Contact support for early access.
Connect an agent in two minutes
The fastest path is the hosted cloud endpoint with OAuth, no install and no key to copy:Frequently asked questions
Can an AI agent create and run a voice agent on SmartAlex?
Yes. Through the MCP server, an assistant callssmartalex_create_agent with a website URL or a company name, and SmartAlex analyzes the business, generates a prompt, and deploys a live voice agent in about 30 to 60 seconds. The assistant can then assign a phone number, add the agent to a campaign, add contacts, and start outbound calling, all in one conversation.
How does SmartAlex keep an AI agent inside its own workspace?
Every credential resolves to exactly one workspace. An API key belongs to the workspace where it was created, and an OAuth token resolves to the user’s active workspace. The API gateway scopes every read and write to that workspace, so a connected AI agent can never see or change another tenant’s contacts, agents, campaigns, or calls. Isolation is enforced at the gateway, not left to the client.Which SmartAlex actions are read-only versus write?
Of the 28 tools, 14 are read-only (all list and get tools, number search, platform status, and widget code) and 14 are write (create, update, buy, add contacts, start, and delete). The defaultread scope grants only the read tools, and write tools require a key with the write scope. The three delete tools are additionally flagged destructive so cautious clients confirm before running them.
Does SmartAlex have a public REST API for AI agents?
A public REST API is in private beta and coming soon, alongside a TypeScript SDK and outbound webhook events. Today the live programmatic surfaces are the MCP server, which covers the full operational surface an agent needs, and Custom HTTP Tools, which let an agent call your own HTTPS endpoint during a call. Contact support if you need REST API early access.What can an AI agent not do through SmartAlex?
An agent cannot cross workspace boundaries, cannot see the underlying voice providers (agent records report a genericcloud provider), and cannot perform write actions with a read-only key. Requests are rate limited to 100 per minute per workspace, and the three delete tools are flagged destructive so clients can require confirmation. These limits are what make it safe to hand an assistant real access.
Related
MCP server overview
The 28 tools, 7 resources, and 5 prompts, and how the pieces fit together.
Getting started
Connect Claude, ChatGPT, Cursor, or Gemini to SmartAlex in under two minutes.
Tools reference
Every tool with its parameters, examples, and response shapes.
What is MCP?
A plain-language explainer of the Model Context Protocol.