Skip to main content
Glama
Sign In
ai-care-agent-mcp

ai-care-agent-mcp

by caresolace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ai-care-agent-mcp

Headless care coordination agent: MCP tools and A2A skills for case-aware, multi-pathway provider search, powered by ai-carematch. Case-management API integration is planned for later phases.

Documentation

Related MCP server: FHIR MCP Server

Quick start

uv sync --dev --group test
cp .env.example .env   # set CAREMATCH_BASE_URL
make verify
make run-mcp           # stdio MCP server

Layout

src/ai_care_agent_mcp/
├── mcp/          # FastMCP tools + registry
├── carematch/    # upstream HTTP adapter
├── case/         # case profile resolution (Phase 2)
├── pathways/     # pathway catalog
├── core/         # settings, errors, logging
└── a2a/          # Agent Card (Phase 3)

Status

Phase

Name

Status

0

Foundation

Complete

1

Carematch MCP MVP

In progress — schemas, OpenAPI pin, validation

2

Case-backed search

Planned

3

A2A + HTTP + AWS IaC

Planned — ECS, API Gateway, Terraform

4

Case-management APIs

Planned

Details: docs/plan/phased-delivery.md.

Available Tools

4 tools
get_case_search_contextC

Resolve a case_ref to search criteria without executing search.

Inputs: case_ref (required), pathway, correlation_id, search_criteria. Returns: result

health_checkA

Report agent health and upstream carematch /health status.

Inputs: no named parameters. Returns: result

list_search_pathwaysA

Return supported search pathways and required field hints.

Inputs: no named parameters. Returns: result

search_providersC

Run a pathway provider search using case_ref, search_criteria, or both.

Inputs: pathway, case_ref, correlation_id, search_criteria. Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    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

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct and well-defined purpose: resolving case references, checking health, listing pathways, and searching providers. No two tools overlap in functionality.

    Naming Consistency4/5

    All tool names use snake_case and are mostly verb_noun (get_, list_, search_), with the exception of health_check which is a noun phrase, but still follows the same style.

    Tool Count4/5

    Four tools is a reasonable count for a focused care agent server. It covers the essential operations without being sparse or excessive.

    Completeness4/5

    The tool set covers the core workflow of obtaining search context, listing pathways, and searching providers. A health check is included. Minor gaps exist (e.g., no direct CRUD for cases), but the surface is adequate for its stated purpose.

    Resources

    Related MCP Connectors

    Related MCP Servers

    • AgentCare

      Kartha-AI
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides healthcare tools for interacting with FHIR data and medical resources on EMRs like Cerner and Epic
      2
      MIT

    • FHIR MCP Server

      jcafazzo
      F
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive MCP server that bridges AI applications with FHIR healthcare data systems, enabling patient data access, clinical data retrieval, and data quality assessment.
      4
      -

    • NPPES MCP Server

      rradhakr-git
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for searching healthcare providers in the US National Provider Identifier (NPI) Registry, enabling natural language queries for provider data in MCP-compatible AI assistants.
      Apache 2.0