DaySmart MCP server
Related Servers
Alternatives to DaySmart MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to find, book, and cancel salon appointments via SalonRunner accounts. Self-hosted for local or remote use.639 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to look up businesses, find free appointment slots, book, list and cancel appointments at salons, barbershops, nail and brow studios and clinics. Works read-only without a customer login by returning a pre-filled booking link, and can also run against a built-in demo with sample businesses.5MIT
- AlicenseNot gradedqualityDmaintenanceConnects AI agents to Coordinalo's scheduling platform, enabling booking management, availability checks, client management, and reporting through MCP tools.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to work in a user's signed-in Paired Plus account, reviewing appointments, client records, and inventory and performing browser actions without a Paired Plus API key. It can connect through hosted HTTP or local stdio MCP transports for Claude, ChatGPT, Cursor, and other agents.Elastic 2.0
- AlicenseAqualityCmaintenanceLets AI agents work inside your own signed-in RazorSync account, so you can schedule and reassign jobs, create work orders, turn completed work into invoices, and follow up on unpaid bills using plain language. Works with Claude Code, ChatGPT, Cursor, and any MCP-capable agent, with a local stdio server that forwards tool calls to the hosted endpoint.7Elastic 2.0
- AlicenseAqualityBmaintenanceEnables AI agents and scripts to run a Booksy Biz account through your own signed-in Chrome session, exposing 28 tools for appointments, open slots, time off, clients, services, staff, reviews, Message Blasts, and reports over MCP, REST, or Python. Read-only mode and confirmation-gated client-facing actions let you plan schedules, reschedules, and outreach with human approval.228102 PyPI6Elastic 2.0
TDQS
Scored across 7 tools
Each tool maps to a distinct step: guide (docs), status (readiness), and the five browser primitives (open/read/click/type/close) are clearly separated by resource and action. The only mild overlap is between daysmart_guide and daysmart_status, since both are framed as 'call this first' setup-style tools, but their purposes (instructions vs. account/connection check) remain distinguishable.
All seven tools share a uniform daysmart_ prefix with short, lowercase, single-token names, giving a very predictable pattern. Minor deviation: guide and status are nouns while open/read/click/type/close are verbs, so the action-style grammar isn't perfectly uniform.
Seven tools is a tight, well-scoped set for a browser-driven SaaS automation surface, with no redundant or filler entries. Onboarding, session control, and page interaction are each covered by exactly the tools needed.
The core loop (open, read, click, type, close) is present, but common browser operations are missing: navigation to a different URL or back, scrolling when content exceeds the visible page, keyboard keys (Enter/Escape/Tab) and dropdown/select handling, and any screenshot or verification affordance. These gaps create plausible dead ends in multi-step appointment/client/pet workflows.