The Local MCP SDK runs the Eka MCP server as a process on your machine. Your AI client talks to it over stdio — no network exposure, no OAuth browser flow. Credentials are passed via environment variables.
Use this when you:
Are building a custom integration or automation pipeline
Need to run offline or in a controlled environment
Want to embed Eka MCP tooling into your own application
Prefer client credentials over OIDC login
Prerequisites
Python 3.10 or higher
Verify your Python version:
Get your API credentials
You need a Client ID and Client Secret from the Eka developer console.
Get your Client ID and Client Secret from the Eka Console
If you need access to a specific workspace (clinic), get an API Key from the Hub
Step 1 — Install the SDK Create an isolated virtual environment first to avoid dependency conflicts: python3 -m venv venv source venv/bin/activate # macOS / Linux # venv\Scripts\activate # Windows pip install "git+https://github.com/eka-care/eka-mcp-sdk.git@main"
Keep the virtual environment activated whenever you run or configure the server. The eka-mcp-server command is only available inside the active venv.
uv add "eka-mcp-sdk @ git+https://github.com/eka-care/eka-mcp-sdk.git@main"
If you don’t have uv yet: curl -LsSf https://astral.sh/uv/install.sh | sh
Only needed if you want to modify the SDK source code : git clone https://github.com/eka-care/eka-mcp-sdk.git cd eka-mcp-sdk python3 -m venv venv source venv/bin/activate # macOS / Linux # venv\Scripts\activate # Windows pip install -e .
An editable install means changes you make to the source are reflected immediately without reinstalling. Verify the install:
You should see the server’s CLI options printed.
Pick your AI client below. Each config passes your credentials as environment variables directly — no .env file required.
Never commit your EKA_CLIENT_ID, EKA_CLIENT_SECRET, or EKA_API_KEY to version control. Add your config file to .gitignore if it contains credentials.
Claude Desktop
Cursor
VS Code
Windsurf
Zed
Open your Claude Desktop config file and add the eka-care server: Config location: ~/Library/Application Support/Claude/claude_desktop_config.jsonclaude_desktop_config.json
{ "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" , "EKA_API_BASE_URL" : "https://api.eka.care" } } } }
Config location: %APPDATA%\Claude\claude_desktop_config.jsonclaude_desktop_config.json
{ "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" , "EKA_API_BASE_URL" : "https://api.eka.care" } } } }
Restart Claude Desktop after saving. The Eka MCP tools will appear in your conversation. Config location: ~/Library/Application Support/Cursor/User/globalStorage/mcp.json{ "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" , "EKA_API_BASE_URL" : "https://api.eka.care" } } } }
Config location: %APPDATA%\Cursor\User\globalStorage\mcp.json{ "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" , "EKA_API_BASE_URL" : "https://api.eka.care" } } } }
Or use the UI: Cmd/Ctrl + Shift + P → Cursor Settings → Tools & MCP → New MCP Server and paste the config above. Create or edit .vscode/mcp.json in your workspace (or add to your user settings.json): { "servers" : { "eka-care" : { "type" : "stdio" , "command" : "eka-mcp-server" , "env" : { "EKA_CLIENT_ID" : "your_client_id" , "EKA_CLIENT_SECRET" : "your_client_secret" , "EKA_API_KEY" : "your_api_key" , "EKA_API_BASE_URL" : "https://api.eka.care" } } } }
Requirements: VS Code 1.95+ with GitHub Copilot enabled.Config location: ~/.codeium/windsurf/mcp_config.json{ "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" , "EKA_API_BASE_URL" : "https://api.eka.care" } } } }
Config location: %APPDATA%\.codeium\windsurf\mcp_config.json{ "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" , "EKA_API_BASE_URL" : "https://api.eka.care" } } } }
Edit ~/.config/zed/settings.json: { "context_servers" : { "eka-care" : { "command" : { "path" : "eka-mcp-server" , "args" : [], "env" : { "EKA_CLIENT_ID" : "your_client_id" , "EKA_CLIENT_SECRET" : "your_client_secret" , "EKA_API_KEY" : "your_api_key" , "EKA_API_BASE_URL" : "https://api.eka.care" } } } } }
Step 3 — Verify Restart your AI client. Then send a test prompt:
Search for patient [name]
The AI should call search_patients and return results from your Eka.care workspace.
Troubleshooting
'eka-mcp-server' command not found
The install likely went into a virtual environment that isn’t on your PATH. Either:
Activate the virtual environment first:
source .venv/bin/activate # macOS/Linux .venv\Scripts\activate # Windows
Or use the full path to the binary in your config:
{ "command" : "/Users/you/project/.venv/bin/eka-mcp-server" }
Authentication failed / 401 errors
Double-check EKA_CLIENT_ID and EKA_CLIENT_SECRET have no extra spaces or quotes
Ensure EKA_API_KEY matches the workspace you’re trying to access
Credentials are available at console.eka.care/api-keys and hub.eka.care
Tools not appearing in the AI client
