procare-mcp
Related Servers
Alternatives to procare-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for the FieldRoutes pest-control / lawn-care operations platform — talk to your data from Claude, Cursor, or any MCP client.MIT
- AlicenseAqualityCmaintenanceA local MCP server that wraps the Housecall Pro Public API, enabling Claude to read and write Housecall Pro data (customers, jobs, estimates, invoices, etc.) via natural language.2340MIT
- AlicenseAqualityBmaintenanceMCP server for the Housecall Pro API, letting AI assistants read and write Housecall Pro data—customers, jobs, invoices, estimates, scheduling, and more—through natural language.440MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes SQL Server databases to Claude, allowing natural language queries with tools to list tables, describe schemas, and run read-only SELECT statements.-
- AlicenseAqualityDmaintenanceA database-agnostic MCP server that enables natural language queries to your database through Claude or Copilot, automatically writing and executing SQL.816MIT
- FlicenseAqualityBmaintenanceMCP server wrapping a mock internal ops platform (FastAPI + SQLite) so Claude Code can read and write employee, project, task, and time data through natural language.8-
TDQS
Scored across 16 tools
Each tool has a clear, distinct purpose: singular get_* for individual records, plural list_* for collections, and health_check for auth verification. No two tools overlap in functionality.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_child, list_schools). The only outlier is health_check, which still follows verb_noun and is standard for such tools.
16 tools cover the major entities (children, classrooms, families, programs, schools, staff, attendance, payments, registrations) without being excessive. The number is well-scoped for a child care management API.
The tool set is entirely read-only (get and list only). No create, update, or delete operations exist for any entity, which is a significant gap for typical CRUD workflows and will cause agent failures when mutation is needed.