Blueprint MCP Server
Related Servers
Alternatives to Blueprint MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables ChatGPT, Claude, and other AI agents to work with client check-ins, workout templates, and training programs in a user's signed-in account, with approval required before actions reach other people.7Elastic 2.0
- AlicenseAqualityDmaintenanceEnables Claude to access IntakeQ practice management data including scheduling, intake forms, treatment notes, invoices, and client records with HIPAA-compliant audit logging.2244 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs and MCP clients to interact with patient records, encounters, and practice information through tools for clinical, scheduling, messaging, and administrative workflows.MIT
- FlicenseAqualityDmaintenanceExposes a clinic's knowledge base and structured records to Claude Desktop as callable tools, with read tools grounded with citations and write tools gated behind approval.4-
- AlicenseAqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceEnables Claude and other AI assistants to trigger HIPAA-compliant patient task management workflows through natural language.1MIT
TDQS
Scored across 7 tools
Each tool maps to a distinct action in a browser session: open, read, click, type, close, plus guide and status for onboarding/readiness. The boundary between guide (how-to) and status (account/credit check) is clearly stated, and no two tools overlap in operation.
All tools share the blueprint_ prefix and snake_case, with mostly verb-based names (open, read, click, type, close). guide and status are noun-style names, a minor deviation from the otherwise consistent verb pattern.
Seven tools is well-scoped for a browser-automation server targeting a single clinical app. Each tool earns its place: session lifecycle, page interaction, plus two support tools for readiness and guidance.
The surface covers the core browser session lifecycle (open, read, click, type, close) and setup/status, leaving no obvious dead ends. Minor gaps exist, such as explicit navigation/scrolling or waiting tools, but agents can work around these with open and repeated read/click calls.