Salonrunner MCP server
io.github.topness-msft/salonrunner-mcp·v0.2.0Self-hosted MCP to find, book, and cancel salon appointments via SalonRunner.
0 stars41 downloads/wk
Reviews
Write oneNobody has reviewed Salonrunner yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Salonrunner tools (6, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
book_appointmentBook an appointment. startTime must be a value returned by find_availability ('YYYY-MM-DD HH:MM:SS'). End time is computed from the provider's service duration. This creates a REAL booking subject to the salon's cancellation policy.
cancel_appointmentwrite actionCancel an existing appointment by appointmentId (from list_my_appointments). Cancellation fees may apply per the salon's policy.
find_availabilityFind open appointment slots for a service in a date range (inclusive). Dates are YYYY-MM-DD. Optionally restrict to one providerId. Returns startable times with the matching provider.
list_my_appointmentsList the signed-in client's upcoming (non-cancelled) appointments.
list_providersList stylists/providers who take online bookings. Optionally filter to those who perform a given serviceId.
list_servicesList bookable services offered by the salon (name, id, price, base duration).
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan9 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 81 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Salonrunner compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 48,255 servers
- Tools
- 6
- the typical server has 7
- Tools that change things
- 17%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 41
- more than 33% of 12,191 servers with a package
What its tools let an agent do: 4 read · 1 create · 1 delete
Install Salonrunner in Claude Code, Cursor or VS Code
Runs npx -y salonrunner-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add salonrunner-mcp -- npx -y salonrunner-mcp
What the publisher says
From the Salonrunner repository's README, as published. We do not edit it. Read it on GitHub
salonrunner-mcp
An MCP server that lets an AI assistant find, book, and cancel salon appointments through your personal SalonRunner / Rosy Salon Software client account — the same booking site many salons use.
It's self-hosted: you deploy your own instance. Run it locally as a tool (Claude Desktop, Cursor, Copilot CLI) where credentials stay on your machine, or as a remote connector for claude.ai where you log in with your SalonRunner account on the connector's login screen.
⚠️ Unofficial, uses undocumented endpoints, personal use only. Read DISCLAIMER.md.
Tools
How it works
list/find/book/cancel
│
this server ──login──► app.salonrunner.com (session cookie)
│ ──authv2─► customer JWT (30 min, auto-refreshed)
│ ──reads──► app.rosysalonsoftware.com/api/v2 (Bearer JWT)
└──────writes───► /customer/appointments/{book,cancel}.json (cookie)customerId is discovered from your account after login; corporateId is read from the JWT. Availability is computed from the provider's per-service duration and the salon's slot grid (SALONRUNNERSLOTMINUTES, default 15).
Configuration
There are two ways to run it, and they get their salon credentials differently:
encrypted into the token — the server needs no salon credentials in its environment.
- Local (stdio): credentials come from the environment (.env).
- Remote (HTTP, claude.ai): credentials are entered on the connector's login screen and
In HTTP mode the salon id + username + password are collected on the login screen (validated by a real SalonRunner login) and encrypted into the OAuth token, so one deployment can serve multiple salons and there are no salon secrets on the server.
Option A — Local (Claude Desktop / Cursor / Copilot CLI)
Published on npm as salonrunner-mcp. Install globally:
npm install -g salonrunner-mcpThen point your client at the salonrunner-mcp command (no build, no absolute paths). Claude Desktop (claudedesktopconfig.json):
{
"mcpServers": {
"salonrunner": {
"command": "salonrunner-mcp",
"env": {
"SALONRUNNER_SALON_ID": "21248",
"SALONRUNNER_USERNAME": "you@example.com",
"SALONRUNNER_PASSWORD": "your-password"
}
}
}
}Prefer no global install? Use "command": "npx" with "args": ["-y", "salonrunner-mcp"] and the same env.
Run from a clone instead
npm install && npm run buildShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Salonrunner: common questions
- Is Salonrunner MCP server safe?
- Mostly: it is graded B (78/100). Read the Salonrunner safety report
- How do I install Salonrunner?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Salonrunner need an API key?
- Yes. The registry entry asks for
SALONRUNNER_PASSWORD. - Is Salonrunner maintained?
- The last commit was 120 days ago (2026-07-07). The latest release is v0.2.0.
- How does Salonrunner compare with other MCP servers?
- safety score 78/100 (higher than 57% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.