Eureka EHR

md.eurekaPublished by eureka.mdOfficial publisherv1.0.0Updated Oct 24, 2026

The Eureka EHR as MCP tools: patients, schedule, notes, messages, billing, and orders.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Remote MCP server exposing the Eureka EHR — patients, schedule, notes, messages, billing and orders — as tools an assistant can call.

What you can do
Work with patient records and demographics in the Eureka EHR. View and manage the practice schedule. Read and write clinical notes. Handle messages. Access billing information and orders.
When to use it
Useful when an assistant should work directly with a Eureka EHR practice: looking up patients, checking the schedule, drafting notes, or reviewing billing and orders without switching systems.
Requirements
A remote MCP endpoint at api.eureka.md over streamable HTTP. Requires a Eureka API key sent as a bearer token in the Authorization header. No local runtime or packages needed.
Before you install
The API key in the Authorization header is a secret and grants access to electronic health record data, including patient information. Tools cover billing and orders as well as notes, so actions may read or change sensitive clinical and financial records; confirm what each tool writes before use.

Installation

In SourceWeft

  1. Open Eureka EHR in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/md.eureka%2Feureka/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "eureka-ehr": {
      "type": "http",
      "url": "https://api.eureka.md/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Eureka integrations