Eka MCP Server

What it is

A connector to medical knowledge bases curated for the Indian healthcare context, built to fix a specific gap: India has no centralised public repository of branded medications, so general models answer drug questions without anything underneath them. The tools are curated by eka.care's in-house doctors and validated against an internal questionnaire.

What you get

• Indian branded drug search — look up across 500,000+ branded drugs by name or generic composition, narrowed by drug form and volume, with generic composition and manufacturer returned
• Indian pharmacology details — a generic composition's details against the 2011 guidelines published by the National Formulary of India
• Indian treatment protocol search — standardised guidelines and decision pathways covering 175 medical conditions across 180 treatment protocols from bodies such as ICMR and RSSDI, retrieved by condition, then by publisher, then by query

Requirements

A developer key from eka.care — a client ID and client secret from console.eka.care, passed as --client-id and --client-secret alongside --eka-api-host in the client config. The code is open source but the APIs behind it are not: valid credentials are required, free access was offered initially, and the project says API usage will be charged in future. Install uv and run through uvx eka_mcp_server; if the client reports spawn uvx ENOENT, use the full path from which uvx as the command. uv cache clean eka_mcp_server forces a newer version when an old one is pinned in the cache. The project states plainly that this is information rather than medical advice, that clinical judgment remains the professional's, and that completeness is not guaranteed for newly approved medications or recently updated guidelines.

Setup effort

One command plus credentials — uvx eka_mcp_server, then supply credentials

Requires

uvx on PATH

Where it runs

The documented client runs the server on your machine.