Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@bahmni-mcp fetch patient with ID 1001"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for Bahmni — exposes the OpenMRS/Bahmni REST API as tools that Claude can call directly.
Install uv if you don't have it:
curl -LsSf https://astral.sh/uv/install.sh | shRelated MCP server: OpenAPI MCP Server
Add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"bahmni": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/lingeswaranTW/bahmni-mcp-server.git",
"bahmni-mcp"
],
"env": {
"BAHMNI_URL": "https://your-bahmni-instance/openmrs/ws",
"BAHMNI_USER": "your_username",
"BAHMNI_PASSWORD": "your_password"
}
}
}
}Claude Code users: edit
~/.claude.jsonand add the samemcpServersblock.
Restart Claude Desktop. No files to download — uvx fetches and runs the server automatically.
Variable | Description |
| Base URL of your Bahmni instance (e.g. |
| Bahmni username |
| Bahmni password |
Bundles observations, diagnoses, orders, and dispositions into a single transaction.
Inputs: body.
Create or update patient demographics and identifiers.
Inputs: body.
Void/delete an encounter
Inputs: uuid (required).
Search for encounters by parameters.
Inputs: body.
Get address hierarchy entry
Inputs: uuid (required).
Get all locations
Inputs: no named parameters.
Get diagnoses for a patient.
Inputs: no named parameters.
Get disease templates for a patient.
Inputs: body.
Get disposition rules (admit/discharge/transfer).
Inputs: no named parameters.
Get drug details
Inputs: uuid (required).
Get drug orders for a patient.
Inputs: no named parameters.
Get observations for a visit or an encounter.
Inputs: concept, visitUuid, encounterUuid.
Get patient by UUID
Inputs: uuid (required).
Get current session info or validate authentication.
Inputs: no named parameters.
Get visits for a patient
Inputs: patient.
Manage, open, or close visits.
Inputs: no named parameters.
Search standard concepts
Inputs: q.
Search patients
Inputs: q.
Search concepts/terminology
Inputs: term, limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 19 tools
Most tools target distinct resources (patient, encounter, observation, etc.), but createOrUpdateEncounterTransaction bundles multiple data types including diagnoses and orders, causing potential overlap with individual getters. Overall, tools are mostly distinct.
All names use camelCase and start with verbs (get, search, createOrUpdate), but verb choice is inconsistent (e.g., findEncounters vs getVisitsForPatient, manageVisits is vague). The pattern is readable but could be more uniform.
19 tools is a reasonable scope for a healthcare MCP, covering core entities without being excessive. The count feels appropriate for the domain.
The tool surface heavily favors read operations; write operations are limited to patient profiles and a single composite encounter transaction. Missing separate create/update for observations, diagnoses, orders, etc., which will cause agent failures in common workflows.
Hosted MCP server for Cliniko — patients, appointments, availability, and invoices for AI agents.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
