The Swift AI Connector is a remote Model Context Protocol (MCP) server that allows AI assistants to securely access your facility's live Swift data using natural language.

Instead of manually searching through reports or customer records, you can simply ask questions like:

How much revenue did we generate last month?
Which customers still have unused credits?
What does tomorrow's schedule look like?

The AI Connector works with any MCP-compatible client, including Claude, Cursor, VS Code, Codex, Windsurf, and Zed.

Overview

The Swift AI Connector gives AI assistants secure, read-only access to your Swift account, allowing them to answer questions using your live facility data. It provides access to:

Live facility data: bookings, customers, revenue, invoices, credits, payroll, and more, read straight from Swift.
Your help centre: The connector also includes every Swift Help Centre article, allowing your AI assistant to explain how to perform tasks in Swift as well as answer questions about your facility's data.
Permission-aware access: Every staff member signs in using their own Swift account. The connector automatically respects each person's existing Swift permissions, so users can only access the information their staff role already allows.
Read-only access: The AI Connector cannot create, edit, or delete anything in your Swift account. This version is strictly read-only.

Before you start

Before setting up the AI Connector:

Your facility must be on the Growth or Scale plan.
The AI Connector (MCP) must be enabled for your facility. If you don't see it, please contact the Swift Support team

Each staff member connects using their own Swift login credentials. There are no shared API keys, passwords, or access tokens to manage,

Find your server URL

Each facility has its own unique server URL. To find yours:

In Swift, navigate to Settings → Integrations
Open the AI Connector (MCP) card.
Copy your Server URL.

Throughout the setup instructions below, replace YOUR_SERVER_URL with your own server URL.

Set up your client

Claude (web and desktop)

Open Settings in the sidebar.
Go to Connectors and choose Add custom connector.
Enter a name such as Swift and paste your server URL.
Sign in with your Swift account and approve access.
Enable the connector in a new chat.

Claude Code

claude mcp add --transport http swift YOUR_SERVER_URL

Run /mcp in a session to complete sign in and confirm the connection.

Cursor

Open Cursor Settings, then Tools & MCP.
Choose New MCP Server and add the configuration below.

{   "mcpServers": {     "swift": {       "url": "YOUR_SERVER_URL"     }   } }

VS Code

Press Cmd/Ctrl + Shift + P and search for MCP: Add Server.
Choose the HTTP transport and paste your server URL.
Name it Swift.

Codex

codex mcp add swift YOUR_SERVER_URL

Windsurf and Zed

These clients connect to local servers only, so they need a bridge. Add this as the command in the client's MCP configuration:

npx mcp-remote YOUR_SERVER_URL

Other clients

Any client that supports MCP over Streamable HTTP can connect. Point it at your server URL and it will walk you through signing in to Swift.

Available tools

The assistant picks the right tool for your question, so you never call these directly. Which tools appear depends on your role, so a front desk account sees fewer than an owner.

Area	Tools	What it covers
Facility	4	Facility details, rooms, schedules, equipment
Services and add-ons	14	Rentals, lessons, classes, camps, packages, memberships, add-ons
Bookings and availability	4	Bookings, booking details, availability events
Customers	2	Customer search and full customer records
Billing and scheduled payments	4	Recent charges, revenue summaries, scheduled billing
Invoices	2	Invoice lists and details
Credits and wallets	3	Customer credits and wallet balances
Reports	2	Revenue and booking reports over any date range
Staff and payroll	3	Staff records and pay rates
Marketing	4	Coupons, email blasts, gift cards, push notifications
Scheduling	2	Service schedules and recurring patterns
Settings	2	Tax rates and custom fees
Retail	1	Products
Help centre	2	Search and read Swift help articles

Example questions

Once connected, you can ask questions such as:

How much revenue did we do last month compared to the same month last year?
Which customers still have unused credits?
What does my Saturday schedule look like?
Who has an invoice outstanding for more than 30 days?
Which lessons had the lowest attendance in June?
How do I bulk import customers into Swift?

Permissions (What data can staff see)

The AI Connector uses the same permission system as Swift.

If a staff member cannot access payroll, financial reports, or customer information inside Swift, they also cannot access it through the AI Connector. No additional permissions are granted.

Also, it is read-only. It cannot create or edit bookings, take payments, message customers, or change any setting.

Managing access

The AI Connector card lists each staff member who has connected, which client they used, and when they last used it.

To disconnect, remove the Swift connector from the client itself, which stops access immediately. Removing someone's staff role in Swift also revokes their access.

Frequently asked questions related to Swift AI Connector

Do I need a separate login or an API key?

No. You sign in with your normal Swift account, and the connector inherits your existing permissions. There is nothing to copy or store.

Can it change anything in my account?

No. Version 1 is read only.

Can other facilities see my data?

No. Each facility has its own server URL, and a connection is scoped to the facility in that URL. Staff at other facilities cannot reach your data.

Which AI tools work with this?

Any client that supports MCP over Streamable HTTP. We have verified Claude and Cursor; others that follow the specification should work without changes on our side.

Why does the assistant say it cannot find something?

Usually the data is outside what your role can see, or the question needs a narrower date range. Try naming the specific period or service.

Nothing happens when I add the connector.

Check you pasted the whole server URL, including the long identifier at the end. Some clients also need a restart after adding a server.