← All integrations

SuperSaaS MCP server

20 operations0 webhooks

Appointment scheduling API for managing users, bookings, slots, and schedules.

Try SuperSaaS with your agent

Connect SuperSaaS, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in SuperSaaS on my account, then run one read-only example and show me the result.

Runs once, when you ask

SuperSaaS tools and triggers

Tools are what your agent can do in SuperSaaS through Corsair's MCP server. Triggers are the SuperSaaS events a routine can start from.

Users

  • CreateWrite

    Create a user. The name is the login name and is the only required field; SuperSaaS assigns the id and returns it in a Location header

    users.create

  • Create With KeyWrite

    Create a user under a key you choose. Reusing that key updates the existing record instead of creating another

    users.createWithKey

  • DeleteDestructive

    Delete a user. Their login stops working and their bookings lose the link, and this cannot be undone

    users.delete

  • GetRead-only

    Read one user by SuperSaaS id or by your own key in the form 1234fk

    users.get

  • ListRead-only

    List the users on the account, paging with limit and offset; more than 1000 records needs offset

    users.list

  • UpdateWrite

    Update a user. A PUT to an unknown id creates it unless notfound says otherwise, so an update can silently become a create

    users.update

Bookings

  • CreateDestructive

    Book an appointment; SuperSaaS may email the customer a confirmation, depending on the schedule settings. A resource schedule needs start and finish, a capacity schedule needs a slot id

    bookings.create

  • DeleteDestructive

    Delete a booking, which frees its time for someone else and cannot be undone

    bookings.delete

  • GetRead-only

    Read a single booking by id

    bookings.get

  • ListRead-only

    List bookings for a schedule, optionally within a start and finish window (resource and service schedules)

    bookings.list

  • UpdateDestructive

    Change a booking's time or details; SuperSaaS may email the customer about the change, depending on the schedule settings

    bookings.update

Slots

  • CreateWrite

    Create a slot on a capacity schedule, which appointments are then booked into

    slots.create

Connect SuperSaaS to Claude, ChatGPT or Cursor

  1. 1

    Connect SuperSaaS in Corsair

    Add your SuperSaaS API key once in Corsair. Corsair stores the credential encrypted and makes the SuperSaaS API calls for your agent, so it never goes into a prompt or a config file. Connect SuperSaaS

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs SuperSaaS. On a ChatGPT personal plan, connect SuperSaaS here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, SuperSaaS's read and write operations run right away and its 5 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/supersaas, add the SuperSaaS plugin, and connect with an API key. Then call methods like corsair.supersaas.api.bookings.create() from your app. Corsair keeps each tenant isolated.

Yes. SuperSaaS requires an API key from your SuperSaaS account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit SuperSaaS, GitHub, Notion, Stripe, and the rest. Trigger SuperSaaS from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for appointment scheduling API for managing users, bookings, slots, and schedules. Common builds include sync jobs, admin tooling, and agents that call SuperSaaS APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per SuperSaaS API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/supersaas in the open repo. When SuperSaaS ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your SuperSaaS data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store SuperSaaS data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put SuperSaaS on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 5 destructive SuperSaaS operations. You can change a link's mode at hub.corsair.dev/me.