Skip to main content
Glama

Related Servers

Alternatives to Blueprint MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude to access IntakeQ practice management data including scheduling, intake forms, treatment notes, invoices, and client records with HIPAA-compliant audit logging.
      22
      44 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs and MCP clients to interact with patient records, encounters, and practice information through tools for clinical, scheduling, messaging, and administrative workflows.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Exposes 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
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      7
      Elastic 2.0

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.