Skip to main content
Glama

Related Servers

Alternatives to therapie-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive reference implementation demonstrating all features of the Model Context Protocol (MCP) specification, serving as documentation, learning resource, and testing tool for MCP implementations.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-first MCP server for research on AI-assisted browsing of a user-owned professional-network account (e.g., LinkedIn), providing read-focused tools such as profile, company, search, and feed reads.
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      A Model Context Protocol server that enables integration with the Teamtailor API, allowing users to list, filter, and retrieve candidate information from their Teamtailor recruitment platform.
      2
      15 npm
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for the University of Vienna's course catalogue (u:find), enabling natural language queries for courses, programmes, staff, and schedules. Read-only, no account or API key required.
      13
      MIT

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation4/5

    The tools split cleanly into search/profile, preferences, shortlist, drafts, contacts, appointments, and a workflow summary. A few pairs touch adjacent local state (save_therapist vs update_saved_therapist, log_contact vs record_appointment, get_shortlist vs workflow_overview), but the descriptions make their boundaries clear.

    Naming Consistency4/5

    Nearly all tools use snake_case verb_noun patterns such as get_, search_, save_, update_, delete_, draft_, log_, record_, list_, and export_. Minor deviations are workflow_overview as a noun phrase and mixing get_shortlist with list_appointments for listing operations.

    Tool Count3/5

    21 tools is heavy for one MCP server, even though they cover several distinct sub-workflows: search, shortlist, drafts, contacts, appointments, preferences, and overview. The grouping is logical, but the surface is large enough that splitting it would improve scoping.

    Completeness4/5

    The main workflow is well covered: search -> profile -> shortlist CRUD -> draft create/read/update/export -> contact/follow-up -> appointment record/list/update/export. Gaps are mostly deletion operations: there is no delete for drafts, contacts/follow-ups, or appointments, and no explicit list of all drafts or follow-ups beyond the overview.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues