Provides medical capabilities through a typed MCP contract.
mcp-medical
Clinical reference and global health intelligence MCP server — search medical literature, retrieve abstracts, explore WHO health indicators, compare country health profiles. 7 tools powered by PubMed and WHO Global…
What it gives an agent
A purpose-built capability behind one MCP connection.
The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.
Architecture
How mcp-medical fits into an agent system.
The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
MCP client
Discovers schemas, sends calls, and receives typed content.
mcp-medical
Validates the request and owns 7 documented tool contracts.
Domain system
Keeps the API, data, credentials, and business rules behind the server.
This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.
Tool catalog
What can an agent ask mcp-medical to do?
Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.
7 named tools
pubmed_searchSearch PubMed for medical literature by topic, condition, or treatment
read onlypubmed_get_abstractGet the abstract of a PubMed article by PMID
read onlywho_get_indicatorGet a specific WHO health indicator for a country
read onlywho_country_profileGet a comprehensive health profile for a country
read onlywho_compare_countriesCompare a health indicator across multiple countries
read onlywho_search_indicatorsSearch available WHO health indicators by keyword
read onlywho_list_common_indicatorsList common WHO health indicator codes and their descriptions
read onlyGovernance
Understand the effect of every tool.
A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.
- The registry manifest declares read only tool risk classes.
MCP surface
What the current documentation declares.
MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.
Install and connect
Follow the project’s documented starting point.
Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.
cargo install mcp-medical{
"mcpServers": {
"medical": {
"command": "mcp-medical"
}
}
}Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.
Official documentation
Continue with the project maintainers’ source of truth.
This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.
Keep exploring
More in industry solutions.
Source record
Release and repository metadata for this catalog entry.
- Version
- 1.0.1
- License
- Apache-2.0
- Tools
- 7
- Revision
- 38a92cf60b70
- Updated
- May 27, 2026