Connect an AI agent

The address

Swum runs an MCP server, the open standard AI tools use to call other apps. Use an MCP client that supports authenticated, stateless Streamable HTTP with JSON responses. The server accepts POST requests; it does not issue sessions or open a GET/SSE stream.

https://api.swum.ai/mcp

Connect in three steps

1. Add the address to your agent. Most tools have a place for an MCP server or a “connector”.
2. The agent opens Sign in with Swum. The school owner signs in, sees what the agent asks for, and picks its pools and its permission level.
3. Done. The agent shows in Settings, Developers & Integrations, AI Agents, where you can change its level, see what it did, or disconnect it.

claude mcp add --transport http swum https://api.swum.ai/mcp

Building your own agent? Sign in with Swum covers the OAuth details.

Steps for your AI app

Every app ends at the same Sign in with Swum page, and only the school owner can allow it. Gemini Enterprise and Microsoft Copilot Studio can't register themselves, so the owner first makes a connector for them in Swum.

Permission levels

You pick one when the agent connects, and can change it any time.

Always asks for approval

Even on Can Act, the agent asks you first before it:

• Cancels a lesson
• Reschedules a lesson
• Moves money, including supported charges, refunds and contractor payments
• Changes pricing or staff permissions
• Sends a broadcast or changes a family message-board post or staff announcement
• Deletes a family or swimmer, merges swimmers, or performs another guarded removal

Tools can also prepare supported enrollment, billing, payroll, school settings and credential-email operations. Each choice describes its validation and approval requirements. Family payment-method management, bulk exports, owner bank-account setup and Swum administrator operations remain outside this connector. Personal family and instructor actions keep their own identity requirements.

Tools

The full catalog has 89 tools covering families, classes, lessons, attendance, payments, progress, waivers, team, messages, schedule, staff, settings, leads and reports. Reports remain read-only. Each operation needs its matching access and current school/location authority. A connected agent sees its permitted tools; Read Only hides business writes. Inputs for every tool.

Waiting for approval

On Ask Me First, a write tool doesn't make the change. It returns pending_approval and the request shows up in Swummy, in the Swum app, with the agent's name on it. You approve or decline there.

{
  "status": "pending_approval",
  "proposalId": "7a1991ec-5e37-43a0-a581-84e817790e4b",
  "proposal_id": "7a1991ec-5e37-43a0-a581-84e817790e4b"
}

Enrollment modes include family-confirmed requests, verified free occurrences and supported approved card/cash enrollment. Read the selected mode's schema and quote instead of treating an approval as proof that payment or enrollment has finished. Meet entries and any family fee checkout also keep their native confirmation steps.

The agent can check with get_proposal_status or the same connection’s GET /v1/proposals/{id}. States include pending, approved, executed, declined, failed and expired. approved means execution started; wait for executed before reporting completion. Proposals expire after 24 hours.

{
  "id": "7a1991ec-5e37-43a0-a581-84e817790e4b",
  "action_type": "SWIMMERS_UPDATE",
  "status": "executed",
  "created_at": "2026-10-26T14:00:00.000Z",
  "result": {
    "message": "Swimmer updated.",
    "changes": {
      "familyId": "family_example",
      "kidId": "swimmer_example"
    }
  }
}