Skip to main content
Windsurf’s Cascade agent can talk to AiSky directly over the Model Context Protocol. Once you add the AiSky MCP server, your coding agent can use AiSky’s tools, as far as your plan and role allow, to build voice agents, wire the widget into whatever app you are shipping, run outbound campaigns, and move deals through the pipeline. This is real Windsurf voice AI: you stay in the editor, describe the outcome, and Cascade drives the account.
AiSky is built for AI-native builders. The MCP server is a first-class surface, so the same connection works across Windsurf, Cursor, Claude Code, and any MCP client. No native “Windsurf plugin” to install: it is a standard remote MCP server.

How the connection works

AiSky runs a hosted MCP server at https://mcp.getsmartalex.com. You sign in to AiSky in your browser, and every call then runs as you, in the workspace you last opened in AiSky, with your role’s permissions. The gateway enforces isolation and rate limits. There is no API key to create.

Add the AiSky MCP server to Windsurf

AiSky works with any MCP app that can connect to a remote server by URL and sign in. Use https://mcp.getsmartalex.com.

Three prompts to try in Cascade

Paste these into Cascade once the server is connected. They map to real tool flows, so the agent will ask for the details it needs and then execute.
When Cascade returns the widget snippet, it is the same one-line script tag AiSky generates for any site:
For a React or Next.js project, inject it from your root layout instead. See widget install for the component pattern.

What the agent can do

The server exposes 103 tools (all prefixed smartalex_), 7 read-only resources, and 5 prompt templates. 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:
Deletes are permanent. Before one runs, the server returns a preview of exactly what will be deleted, and Cascade must show it to you and wait for your yes. Read the preview before you approve, and be careful with settings that run tools without asking. See Security and permissions. Rate limits are 100 requests per minute per workspace.
The voice stack is curated, high-accuracy speech, language, and voice models, kept abstracted behind the platform. Agent records report voice_provider: "cloud". You operate voice agents through AiSky without assembling or tuning any underlying components yourself.

Webhooks and custom HTTP tools

Cascade can create webhook subscriptions through MCP (this needs the Power Tools add-on), and each subscription returns an HMAC-SHA256 signing secret once at creation for verifying delivery. Named events include contact.created, contact.updated, contact.deleted, deal.created and deal.stage_changed.
Subscription management and event delivery for contacts and deals are live today. A dedicated call.completed event is coming soon; until then every call sends contact.updated for the caller. For live in-call integrations, use Custom HTTP Tools (part of Power Tools), which let an agent call your own HTTPS endpoint mid-call. The public REST API is live with read-only keys, and a TypeScript SDK is coming soon.

MCP getting started

Full setup across every MCP client.

Tools reference

Every one of the 103 tools with inputs and outputs.

Build with Cursor, v0 and Bolt

The same MCP flow in other agentic editors.

Build with Claude Code

Connect the hosted server over OAuth from the CLI.