Skip to main content
Glama
jbonjour

bmlt-mcp-server

by jbonjour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to bmlt-mcp-server

No user-submitted related servers found.

    Related Servers

    • FHIR MCP Server

      lKaya5473
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients and LLM-based agents to interact with FHIR-compliant healthcare backends via natural-language prompts, supporting full CRUD operations on FHIR resources, document ingestion, semantic search, and LOINC terminology lookup.
      -

    • onemap8-mcp

      evallgar
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes OneMap8 fleet tracking to AI clients, enabling natural-language queries about devices, positions, reports, geofences, drivers, and more. Includes 32 tools, permission scoping, and safety guardrails.
      -

    • halaxy-mcp

      ryanhunt
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets AI assistants query your Halaxy practice-management data—appointments, invoices, referrals, and practitioners—via natural language, exposing read-only tools for daily schedules, billing status, and session limits.
      GPL 3.0

    • mindbody-mcp

      NoBanks
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Mindbody, enabling AI agents to fetch client info, query class schedules, book classes/appointments (env-gated), and process checkout (payment-gated).
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: formats, meeting details, server info, service bodies, and search. There is no overlap, and an agent can easily select the right tool for a given task.

    Naming Consistency5/5

    All tool names follow the predictable pattern 'bmlt_verb_noun' (e.g., bmlt_get_formats, bmlt_search_meetings). The convention is consistent and readable.

    Tool Count5/5

    Five tools is an appropriate number for a read-only meeting information server. Each tool serves a necessary function without being excessive or insufficient.

    Completeness5/5

    The tool set covers all primary operations for querying BMLT meeting data: retrieving metadata (server info, service bodies, formats), searching meetings, and getting detailed records. No obvious gaps exist for the intended read-only use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources