Skip to main content
Glama
kriskraw80

Connects to Epic MyChart patient portals to log in, list test results, and download them as PDFs so an AI assistant can help understand your own lab work.

by kriskraw80
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Connects to Epic MyChart patient portals to log in, list test results, and download them as PDFs so an AI assistant can help understand your own lab work.

No user-submitted related servers found.

    Related Servers

    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.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct role: configure provider, login, check session, list results, get detail, download PDF, screenshot for debugging, and close browser. No overlapping purposes that would confuse an agent.

    Naming Consistency4/5

    All tools share the 'mychart_' prefix and most use verb_noun (set_provider, list_test_results, get_test_result, download_test_result, close_browser). Minor deviations include 'login', 'session_status', and 'screenshot', but the pattern remains recognizable and predictable.

    Tool Count5/5

    Eight tools is a well-scoped size for a MyChart portal connector. Each tool covers a necessary step in the workflow (setup, auth, status, list, retrieve, download, debug, cleanup) without redundancy or bloat.

    Completeness5/5

    The tool set fully covers the stated purpose: configure a provider, log in, verify session, list test results, retrieve readable content, download PDFs, and debug if scraping fails. There are no obvious gaps for the intended use case.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources