Medical Knowledge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOWLEDGE_BASE_PATH | Yes | Path to the knowledge base directory (required for loading medical files) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_file_contentA | Get the complete content of a specific file by name. Useful when you need to read full documentation. |
| search_filesA | Search across all knowledge base files for specific keywords or phrases. Returns relevant excerpts with context. |
| calculate_health_scoreB | Calculate comprehensive health scores based on patient parameters using the 8-system framework. Returns normalized scores, system breakdowns, and interpretation. |
| recommend_smart_cardsB | Find relevant SMART cards (medical and behavioral interventions) for a specific condition or health goal. |
| generate_care_planA | Generate a personalized care plan based on patient age, conditions, and goals using Performance Medicine framework. |
| refresh_knowledge_baseA | Manually refresh the knowledge base to detect newly added files. Usually not needed as file watching is automatic. |
| check_git_statusA | Check Git status of repositories (knowledge base and/or MCP server). Shows current branch, uncommitted changes, and available updates. |
| pull_git_updatesB | Pull latest changes from Git remote for knowledge base and/or MCP server. Automatically refreshes knowledge map after pulling knowledge base. |
| sync_repositoriesA | One-click sync: Check status and pull updates for all repositories. Can be used in check-only mode to see what updates are available. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explain_health_system | Explain how a specific health system is assessed using the 8-system framework |
| analyze_parameters | Analyze health parameters and provide detailed interpretation using the scoring framework |
| manage_condition | Provide comprehensive condition management approach using SMART cards and Performance Medicine protocols |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Medical Knowledge Base - Complete Index | Hierarchical index of all medical knowledge files with summaries. This resource is automatically loaded and provides an overview of the entire knowledge base. |
TDQS
Scored across 9 tools
The clinical tools (calculate_health_score, recommend_smart_cards, generate_care_plan) are distinct, but the repository maintenance tools overlap: sync_repositories essentially combines check_git_status and pull_git_updates, and pull_git_updates vs refresh_knowledge_base both have refresh effects. The descriptions help, but an agent could easily select the wrong sync/pull/check tool.
All nine tools follow a consistent verb_noun snake_case pattern (calculate, recommend, generate, refresh, check, pull, sync, get, search). This makes the tool set predictable and easy to navigate.
Nine tools is well within the ideal range and each tool serves a clear purpose in either clinical reasoning or knowledge base maintenance. The count feels appropriately scoped for a medical knowledge server.
The surface covers core clinical workflows (scoring, interventions, care plans) and knowledge base maintenance (search, read, refresh, git sync). Minor gaps exist, such as no tool to list all available files or directly edit knowledge content, but these can be worked around via git and file operations.