nisebookings

com.nisebookingsPublished by nisebookings.comOfficial publisherv1.0.0Updated Oct 24, 2026

Operate a nisebookings account: catalogue, staff schedules, free slots, customers, appointments

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP endpoint for nisebookings that lets an assistant work with a booking account's catalogue, staff schedules, free slots, customers and appointments.

What you can do
  • Manage the service catalogue and staff schedules in a nisebookings account
  • Look up free slots and book or review appointments
  • Access customer records tied to bookings
  • Operate the account through the hosted nisebookings endpoint
When to use it
Useful when you run bookings through nisebookings and want an assistant to check availability, handle appointments or look up customers without switching to the admin interface.
Requirements
A remote MCP connection to the nisebookings endpoint over streamable HTTP. A nisebookings account and a Management API key from Settings → API, sent as a bearer token in the Authorization header.
Before you install
The Management API key grants access to the booking account and its customer data; keep it secret and revoke it if exposed. The server can change catalogue, schedule and appointment data, so confirm write actions before running them. Customer records are personal data handled by a third-party service.

Installation

In SourceWeft

  1. Open nisebookings in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.nisebookings%2Fbooking/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.

{
  "mcpServers": {
    "nisebookings": {
      "type": "http",
      "url": "https://app.nisebookings.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 13, 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.