StyleSeat MCP server
Related Servers
Alternatives to StyleSeat MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects a signed-in SalonBiz account to ChatGPT, Claude, Codex, and Claude Code via Cotlet.dev, enabling users to read appointments, tickets, inventory, payments, and reports and to make booking, online booking, and campaign changes with approval by default.7Elastic 2.0
- AlicenseAqualityBmaintenanceEnables ChatGPT, Claude, and other AI agents to manage appointments, customers, services, staff calendars, and notes in Setmore through natural language via Cotlet.dev.7Elastic 2.0
- AlicenseAqualityCmaintenanceEnables AI agents such as ChatGPT and Claude to manage ClinicSense scheduling, wait lists, payments, reports, and client emails through Cotlet.dev, with write calls requiring approval by default and excluding charting, SOAP notes, intake forms, and client files.7Elastic 2.0
- AlicenseAqualityCmaintenanceEnables ChatGPT, Claude and other AI agents to manage availability, blocked time, forms, invoices and client reports in a signed-in account, with write actions requiring approval by default. It connects through Cotlet.dev either as a hosted endpoint or as a local stdio server that forwards tool calls.7Elastic 2.0
- AlicenseAqualityCmaintenanceConnects a signed-in GoReminders account to ChatGPT, Claude, and other AI agents through Cotlet.dev, letting them read appointments and customer replies, manage reminders, and review booking requests, with write operations requiring approval before they run.7Elastic 2.0
- AlicenseAqualityBmaintenanceConnects AestheticsPro accounts to ChatGPT, Claude, and other AI agents through Cotlet, enabling appointment scheduling, client contact access, lead creation, and staff assignment with user approval.7Elastic 2.0
TDQS
Scored across 7 tools
Each tool maps to a distinct browser-automation action or setup step: status, guide, open, read, click, type, and close. The numbered-element model for read/click/type prevents overlap, and status versus open are clearly separated.
All tools use the styleseat_ prefix followed by a single lowercase verb or noun (status, type, close, guide, open, read, click). The pattern is consistent and predictable throughout.
Seven tools are well-scoped for a browser automation server: setup, page interaction, and session teardown. No redundant tools are present.
Core lifecycle is covered: check readiness, open, read, click, type, close, plus a guide. Minor gaps like explicit scroll, wait, or back navigation exist, but agents can likely work around them via read/click.