Skip to main content
Glama
Emergency Medicare Planner MCP Server

Emergency Medicare Planner MCP Server

by manolaz

Emergency Medicare Management MCP Server

(@manolaz/emergency-medicare-planner-mcp-server)

A powerful Model Context Protocol (MCP) server that integrates with Google Maps to locate and evaluate medical facilities in emergency situations. This server helps users find appropriate hospitals and clinics within 10km radius based on specific medical needs, emergency level, and facility capabilities.

The system provides real-time routing, availability checks, and detailed information about medical services, helping patients make informed decisions during urgent healthcare situations.

Key Feature: Sequential Thinking for Medical Evaluation - Enables step-by-step clinical reasoning for more accurate medical facility matching based on patient symptoms and medical history.

Installation & Usage

Installing via Smithery

To install Emergency Medicare Planner for Claude Desktop automatically:

npx -y @smithery/cli install @manolaz/emergency-medicare-planner-mcp-server --client claude

Installing Manually

# Using npx (recommended)
npx @manolaz/emergency-medicare-planner-mcp-server

# With environment variable for Google Maps API
GOOGLE_MAPS_API_KEY=your_api_key npx @manolaz/emergency-medicare-planner-mcp-server

Or install globally:

# Install globally
npm install -g @manolaz/emergency-medicare-planner-mcp-server

# Run after global installation
GOOGLE_MAPS_API_KEY=your_api_key emergency-medicare-planner-mcp-server

Related MCP server: google_maps_mcp

Components

Tools

  • searchMedicalFacilities

    • Search for hospitals, clinics, and medical facilities using Google Places API

    • Input:

      • query (string): Search query (e.g., "emergency room", "pediatric clinic")

      • location: Latitude and longitude of patient location

      • radius (optional, default: 10000): Search radius in meters

      • specialtyNeeded (optional): Medical specialty required

  • getMedicalFacilityDetails

    • Get detailed information about a specific medical facility

    • Input:

      • placeId (string): Google Place ID of the medical facility

    • Output:

      • Hours of operation, services offered, contact information, etc.

  • calculateRouteToFacility

    • Calculate fastest route to a medical facility

    • Input:

      • origin: Patient's current location

      • facilityId: Place ID of the destination facility

      • transportMode (optional): Travel mode (driving, walking, transit, ambulance)

      • avoidTraffic (optional): Route planning to avoid traffic

  • checkFacilityAvailability

    • Check if a facility is currently accepting patients

    • Input:

      • facilityId: Place ID of the medical facility

      • emergencyLevel: Urgency level of the medical situation

Configuration

Usage with Claude Desktop

To use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json:

{
  "mcpServers": {
    "emergency-medicare-planner": {
      "command": "npx",
      "args": ["@manolaz/emergency-medicare-planner-mcp-server"],
      "env": {
        "GOOGLE_MAPS_API_KEY": "your_google_maps_api_key"
      }
    }
  }
}

Alternatively, you can use the node command directly if you have the package installed:

{
  "mcpServers": {
    "emergency-medicare-planner": {
      "command": "node",
      "args": ["path/to/dist/index.js"],
      "env": {
        "GOOGLE_MAPS_API_KEY": "your_google_maps_api_key"
      }
    }
  }
}

Development

Building from Source

  1. Clone the repository

  2. Install dependencies:

    npm install
  3. Build the project:

    npm run build

Environment Variables

  • GOOGLE_MAPS_API_KEY (required): Your Google Maps API key with the following APIs enabled:

    • Places API

    • Directions API

    • Geocoding API

    • Time Zone API

    • Distance Matrix API

Testing

# Run test suite
npm test

# Run with debug logging
DEBUG=emergency-medicare:* npm start

License

This MCP server is licensed under the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

5 tools
check_medicare_coverageC

Checks what treatments and procedures are covered by Medicare

Inputs: state (required), treatmentCode (required), insuranceType.

find_nearby_medical_facilitiesC

Finds hospitals and clinics nearby user location that match specific requirements

Inputs: userLocation (required), careQuality, facilities, infrastructure, +3 more.

get_emergency_contactsC

Retrieves emergency contact information for a specific location

Inputs: location (required), serviceType.

schedule_emergency_transportC

Arranges emergency medical transportation

Inputs: medicalCondition (required), patientLocation (required), urgency (required), destination.

sequentialthinkingA

A detailed tool for dynamic and reflective medical problem-solving through thoughts. This tool helps analyze medical problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding of the medical situation deepens.

When to use this tool:

  • Breaking down complex medical problems into steps

  • Planning and designing treatment approaches with room for revision

  • Clinical analysis that might need course correction

  • Medical problems where the full scope might not be clear initially

  • Healthcare decisions that require a multi-step solution

  • Medical evaluations that need to maintain context over multiple steps

  • Situations where irrelevant medical information needs to be filtered out

Key features:

  • You can adjust total_thoughts up or down as the diagnosis progresses

  • You can question or revise previous medical assessments

  • You can add more diagnostic thoughts as new information emerges

  • You can express clinical uncertainty and explore alternative approaches

  • Not every medical assessment needs to build linearly - you can branch or backtrack

  • Generates a clinical hypothesis

  • Verifies the hypothesis based on the Chain of Thought steps

  • Repeats the process until a satisfactory diagnosis or treatment plan is reached

  • Provides a correct medical assessment or recommendation

Inputs: nextThoughtNeeded (required), thought (required), thoughtNumber (required), totalThoughts (required), +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 5 tools

    Disambiguation3/5

    Four tools have distinct purposes (coverage check, facility finding, contact retrieval, transport scheduling), but the 'sequentialthinking' tool is ambiguous—it overlaps with the analytical aspects of the other tools and lacks a clear boundary, potentially causing misselection for medical problem-solving tasks. The descriptions help differentiate the core four, but the fifth introduces confusion.

    Naming Consistency2/5

    Four tools follow a consistent verb_noun pattern (e.g., check_medicare_coverage, find_nearby_medical_facilities), but 'sequentialthinking' deviates significantly with a single, non-standard noun. This mixing of conventions (snake_case vs. lowercase compound) reduces predictability and readability across the tool set.

    Tool Count4/5

    With 5 tools, the count is reasonable for an emergency medical planning server, covering key functions like coverage, facilities, contacts, and transport. It's slightly under-scoped as it lacks tools for updating or managing data, but overall, each tool earns its place without feeling excessive or thin.

    Completeness3/5

    The tool set covers core emergency planning aspects (coverage, facilities, contacts, transport) but has notable gaps: there are no tools for updating information (e.g., modify contacts or schedules), managing user profiles, or handling post-emergency follow-ups. The 'sequentialthinking' tool adds analytical depth but doesn't fill these operational gaps, leaving the surface incomplete for full lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables location-aware AI agents to search for nearby places, get detailed place information including hours and ratings, and calculate routes with turn-by-turn directions using Google Maps APIs.
      22
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Google Maps and Places APIs for local businesses and tourist attractions in India through a simple MCP interface.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables emergency medical coordination with tools for triage, medication guidance, blood donor outreach, mass casualty simulation, and emergency plan generation.
      MIT