Oorep MCP Server

MCP server and TypeScript SDK for OOREP homeopathic repertory and materia medica reference data. Exposed over MCP by the oorep mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP server and TypeScript client SDK that gives AI assistants access to OOREP's homeopathic repertory and materia medica reference data.

Adding it to your client

The server ships on npm as oorep-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• Tools — The Tools tool exposed by this server
• search_repertory — The search_repertory tool exposed by this server
• search_materia_medica — The search_materia_medica tool exposed by this server
• get_remedy_info — The get_remedy_info tool exposed by this server
• list_available_repertories — The list_available_repertories tool exposed by this server
• list_available_materia_medicas — The list_available_materia_medicas tool exposed by this server
• Resources — The Resources tool exposed by this server
• Prompts — The Prompts tool exposed by this server
• Wildcards — The Wildcards tool exposed by this server
• Exclusions — The Exclusions tool exposed by this server
• Combined — The Combined tool exposed by this server
• Tips — The Tips tool exposed by this server

Configuration

You will need 5 environment variables: OOREP_MCP_BASE_URL, OOREP_MCP_LOG_LEVEL, OOREP_MCP_TIMEOUT_MS, OOREP_MCP_CACHE_TTL_MS, OOREP_MCP_MAX_RESULTS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js ≥ 20.0.0 - npm ≥ 10.0.0

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Oorep.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the oorep mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Oorep's toolset — Tools, search_repertory, search_materia_medica and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Dhi13man; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.