Eka Care API的MCP工具

Install with development dependencies

uv sync --extra dev

Installation

Install with UV (recommended)

uv sync

Building Hosted Solutions

This SDK supports multi-tenant workspace routing where different clients (Eka, Moolchand, etc.) can use the same tools with their own API implementations.

Usage with Claude Desktop

Add to your Claude Desktop MCP configuration. Important: Use the full path to the virtual environment's Python executable:

{
  "mcpServers": {
    "eka-care": {
      "command": "/absolute/path/to/eka-mcp-sdk/.venv/bin/python",
      "args": ["-m", "eka_mcp_sdk.server"],
      "env": {
        "EKA_CLIENT_ID": "your_client_id",
        "EKA_CLIENT_SECRET": "your_client_secret", 
        "EKA_API_KEY": "your_api_key"
      }
    }
  }
}

Doctor Tools Examples

```python

Running Examples

python examples/direct_usage.py
python examples/crewai_usage.py  # Requires: uv add crewai
cat examples/MCP_USAGE.md

Configuration

Create a .env file:

```env

API Configuration

EKA_API_BASE_URL=https://api.eka.care

Server configuration

EKA_MCP_SERVER_HOST=localhost EKA_MCP_SERVER_PORT=8000 EKA_LOG_LEVEL=INFO ```

Configuration Reference

Eka.care MCP SDK

A Python library and self-hosted MCP server that exposes Eka.care's healthcare APIs to LLM applications. Use it as an importable library in your own projects, or run it directly as a standalone MCP server.

Supported API Modules

API Documentation

eka_mcp_sdk/clients/moolchand_client.py

from .base_emr_client import BaseEMRClient

class MoolchandClient(BaseEMRClient): def get_workspace_name(self) -> str: return "moolchand" # Implement all abstract methods with your API logic async def doctor_availability_elicitation(self, ...): ... async def book_appointment_with_validation(self, ...): ...

**2. Configure via environment:**

Adding New API Modules

1. Create client in eka_mcp_sdk/clients/
2. Implement MCP tools in eka_mcp_sdk/tools/
3. Register tools in server.py
4. Update documentation

Extensible Modules

You can easily add more API modules like: - ABDM Connector: Health ID creation, consent management, health record sharing - Self Assessment: Health surveys, symptom checking, record analysis - Custom Modules: Build your own using the base client architecture

Or alternatively

python -m eka_mcp_sdk.server ```

Alternative Configuration (if eka-mcp-server is in PATH)

If you installed the package globally or added the virtual environment to your PATH:

{
  "mcpServers": {
    "eka-care": {
      "command": "eka-mcp-server",
      "env": {
        "EKA_CLIENT_ID": "your_client_id",
        "EKA_CLIENT_SECRET": "your_client_secret",
        "EKA_API_KEY": "your_api_key"
      }
    }
  }
}

Troubleshooting

Git tag versioning (hatch-vcs) - Tags must follow PEP 440: v0.2.0a1, v0.2.0rc1, v0.2.0.dev1 — not v0.1.0-test - If an invalid tag exists alongside a valid one on the same commit, setuptools_scm may pick the invalid one → delete the bad tag: git push origin --delete <bad-tag> - After fixing tags, clear uv's build cache: uv cache clean

---