Skip to main content
Glama
drdanieldorta

mdia-feegow-mcp

by drdanieldorta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to mdia-feegow-mcp

No user-submitted related servers found.

    Related Servers

    • Ecuro Light API MCP Server

      creeai
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes tools from the Ecuro Light API for managing clinical appointments, patient records, and clinic availability. It enables users to perform healthcare management tasks such as scheduling, patient search, and report generation through MCP-compatible clients.
      -

    • Cliniko MCP Server

      yasboop
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with the Cliniko practice management system through MCP tools and resources. Supports patient management, appointment scheduling, and practice data access through natural language interactions.
      -

    • clinic-mcp-server

      Ariless
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to interact with a clinic booking API, including listing specialties, doctors, and a patient's appointments, and booking or cancelling appointments when the active profile permits, while preserving the caller's authority and screening tool descriptions for safety.
      3
      MIT

    • mcp-brasilapi

      silasrm
      A
      license
      A
      quality
      C
      maintenance
      Exposes the BrasilAPI as MCP tools, enabling AI agents to query Brazilian public data such as CEP, CNPJ, DDD, IBGE, banks, PIX, FIPE, NCM, exchange rates, taxes, weather, CVM information, holidays, ISBN, domains, stock tickers, and TUSS.
      41
      Apache 2.0
    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

    C2.9/5.0

    Scored across 97 tools

    Disambiguation4/5

    Most tools have distinct purposes, aided by category prefixes like [Agendamentos]. However, there is ambiguity between 'feegow_available_schedule' and 'feegow_available_schedule_v2' (two versions with unclear differences), and the large number of appointment-related tools could cause confusion despite distinct descriptions.

    Naming Consistency4/5

    The vast majority of tools follow a consistent 'feegow_verb_noun' pattern (e.g., list_professionals, create_appointment). A few exceptions like 'feegow_dmed', 'feegow_status', and 'feegow_request' deviate from this pattern, preventing a perfect score.

    Tool Count1/5

    97 tools is extremely high for an MCP server, far exceeding the typical 3-15 range. While the Feegow system is complex, this number overwhelms an agent and makes tool selection difficult, warranting the lowest score.

    Completeness2/5

    The tool surface covers many areas (appointments, finances, patients, etc.) but has significant gaps: no tools to create, update, or delete professionals; no delete patient; no single appointment retrieval by ID. These missing CRUD operations will cause agent failures.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources