OOREP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OOREP_MCP_BASE_URL | No | OOREP API base URL | https://www.oorep.com |
| OOREP_MCP_LOG_LEVEL | No | debug | info | warn | error | info |
| OOREP_MCP_TIMEOUT_MS | No | Request timeout (ms) | 30000 |
| OOREP_MCP_MAX_RESULTS | No | Maximum results cap | 100 |
| OOREP_MCP_REMOTE_USER | No | If set, sends X-Remote-User header (numeric member ID) on all upstream requests | |
| OOREP_MCP_CACHE_TTL_MS | No | Cache TTL (ms), 0 to disable | 300000 |
| OOREP_MCP_DEFAULT_REPERTORY | No | Default repertory | publicum |
| OOREP_MCP_DEFAULT_MATERIA_MEDICA | No | Default materia medica | boericke |
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 |
|---|---|
| search_repertoryA | Search for symptoms in homeopathic repertories and return matching rubrics with remedies. Supports wildcards (*), exclusions (-), and exact phrases ("). Returns rubrics sorted by relevance with remedies and their weights. |
| search_materia_medicaA | Search materia medica texts for symptoms and return matching remedy sections. Materia medicas provide detailed descriptions of remedy characteristics, symptoms, and clinical applications. Useful for in-depth remedy study and comparison. |
| get_remedy_infoA | Retrieve comprehensive information about a specific homeopathic remedy including its full name, abbreviations, and alternative names. Useful for learning about individual remedies. |
| list_available_repertoriesA | Get a complete list of all available homeopathic repertories with their metadata including title, author, and language. Useful for discovering which repertories are available for searching. |
| list_available_materia_medicasB | Get a complete list of all available homeopathic materia medicas with their metadata including title, author, and language. Useful for discovering which materia medicas are available for searching. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-symptoms | Guide AI through structured symptom analysis workflow for homeopathic case taking. Helps systematically analyze symptoms and find relevant remedies. |
| remedy-comparison | Compare multiple homeopathic remedies side-by-side to identify the best match. Useful for differential diagnosis between similar remedies. |
| repertorization-workflow | Step-by-step case taking and repertorization workflow for comprehensive case analysis. Guides through symptom gathering, repertorization, and remedy selection. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Remedies List | Complete list of all available homeopathic remedies with names and abbreviations |
| Available Repertories List | List of all accessible repertories with metadata (title, author, language) |
| Available Materia Medicas List | List of all accessible materia medicas with metadata (title, author, language) |
| OOREP Search Syntax Help | Guide to OOREP search syntax including wildcards, exclusions, and exact phrases |
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: two search tools (repertory vs materia medica), a remedy info retrieval tool, and two list tools (repertories vs materia medicas). There is clear separation between discovery (list_*) and usage (search_*, get_*) functions.
Nearly all tools follow a verb_noun pattern (search_repertory, search_materia_medica, get_remedy_info, list_available_*). Minor inconsistency: two tools use singular (search_repertory, search_materia_medica) while their corresponding list tools use plural (repertories, materia_medicas), which is slightly inconsistent but understandable.
Five tools is a well-scoped count for a homeopathic reference server. Each tool serves a distinct purpose covering search, lookup, and discovery without redundancy or bloat.
The tool surface covers the core workflows: discover available repertories/materia medicas, search for symptoms in repertories, search detailed materia medica texts, and retrieve individual remedy info. A minor gap is the lack of a dedicated search-within-remedy or remedy comparison tool, but the primary use cases are covered.