SuperSaaS

com.supersaasPublished by supersaas.comOfficial publisherv1.0.0Updated Oct 24, 2026

Find available slots and manage bookings, users, and forms in the SuperSaaS scheduling service

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Connects an assistant to SuperSaaS scheduling so it can find open slots and manage bookings, users and forms.

What you can do
  • Look up available appointment slots in the SuperSaaS schedule
  • Create and manage bookings
  • Manage user records in the scheduling account
  • Work with forms used for booking intake
When to use it
Useful when you run appointments or resource scheduling on SuperSaaS and want an assistant to check availability or handle bookings and user records without switching to the web interface.
Requirements
A remote MCP endpoint at supersaas.com reached over streamable HTTP. OAuth sign-in is required, so the user needs a SuperSaaS account and must authorize the connection. No environment variables or headers are declared.
Before you install
The assistant can change scheduling data: bookings, users and forms may be created, modified or removed. Access is granted through OAuth to a SuperSaaS account, so review the scopes and permissions granted during authorization and confirm which account is connected.

Installation

In SourceWeft

  1. Open SuperSaaS in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.supersaas%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "supersaas": {
      "type": "http",
      "url": "https://www.supersaas.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Supersaas integrations