pharmguide-mcp
An MCP server that gives Claude and other AI agents the evidence behind Omiclamp:
- Pharmacogenomics (PGx): what published guideline bodies (CPIC, DPWG, the FDA, Health Canada, ClinPGx, with PharmGKB shown verbatim) say about how a person's genes affect a medication. Every evidence row carries its source, citation, link and date.
- Nutrigenomics (NGX): ten gene-diet topics graded for scientific validity against the Grimaldi et al. 2017 framework, with failed replications and guideline dissent surfaced as conflicts.
It runs on your machine. Nothing you ask it, including a genotype, is sent anywhere. The engine and its compiled data ship inside the package, so the answers match www.omiclamp.com for the same build.
Use it for what it is
This is an educational reference, not medical or dietary advice and not clinical decision support. It reports and contrasts what sources say; it does not tell anyone what to take.
- Do not use it to make or automate prescribing, dosing or dietary decisions for a particular person.
- Keep the
educational_disclaimer(ordisclaimer) and the sources attached to anything you show from a response. - Cite the guideline body on each row, not this server, and honour its licence: CPIC is CC BY 4.0; DPWG, ClinPGx and PharmGKB are CC BY-SA 4.0 (share-alike; PharmGKB verbatim only); FDA tables are US public domain.
describe_capabilitiesreturns the full table. - Every response carries
provenancewith the compile date. Say how current the data is.
Install
Needs uv. Nothing else to install: uvx fetches the package on first run.
Claude Code
claude mcp add omiclamp -- uvx pharmguide-mcp
Claude Desktop and other MCP clients
{
"mcpServers": {
"omiclamp": {
"command": "uvx",
"args": ["pharmguide-mcp"]
}
}
}
Tools
| Tool | What it returns |
|---|---|
describe_capabilities |
Call first. Coverage, the meaning of every coded field, source licences and how to cite. |
lookup_drug |
A drug (generic or brand) with its guideline stance, per-source cited evidence, source agreement, conflicts and jurisdictions. |
lookup_pair |
One gene and one drug: the evidence rows for that gene, plus the drug's conflicts. |
translate_genotype |
A star-allele genotype (for example {"CYP2C19": "*1/*2"}) to its CPIC phenotype, from CPIC's diplotype tables. |
list_catalog |
Every queryable drug name, generic and brand. |
ngx_list_topics |
The graded nutrigenomics topics: gene, claim, grade, actionability. |
ngx_lookup_topic |
One topic's full assessment: grade, conflicts, evidence and references. |
Develop
From a checkout of the Omiclamp repository:
cd pharmguide-mcp
PYTHONPATH=..:. python -m pytest -q # includes parity with every record the site serves
PYTHONPATH=..:. python -m pharmguide_mcp.server
./build.sh # wheel + sdist into dist/, engine and data bundled
The server only registers tools and framing (server.py); tools.py delegates to the pharmguide.signal engine and reshapes its output, with no clinical logic of its own. NGX is served from the YAMLs in ngx_data/, kept identical to pharmguide-web/ngx-evidence/.
Release
Bump version in pyproject.toml, merge, then push a matching tag: git tag mcp-v0.3.0 && git push origin mcp-v0.3.0. The Publish MCP server workflow tests, builds and publishes to PyPI. Rebuild and release whenever the compiled data changes, or installed copies keep serving the old evidence.
Metadata
Release files for pharmguide-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pharmguide_mcp-0.3.0.tar.gz | 404.1 kB | Without provenance | Details for pharmguide_mcp-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pharmguide_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for pharmguide_mcp-0.3.0-py3-none-any.whl |
Total release size: 833.7 kB
Release files / pharmguide_mcp-0.3.0.tar.gz
| Download URL | pharmguide_mcp-0.3.0.tar.gz |
|---|---|
| Size | 404.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6186be1f56bf9696a46a071285f330bd6cde2ce530ebe77de4205c392142d97
|
|
BLAKE2b-256 checksum How to use checksums |
f5419cf5491c31828b9b454566d695bb1660b08bf330a94c37ab264b1b926423
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / pharmguide_mcp-0.3.0-py3-none-any.whl
| Download URL | pharmguide_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 429.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d31d53e8068a3077971ed297340bc54069e34b6d1243f17db711ee6d71fb1ad9
|
|
BLAKE2b-256 checksum How to use checksums |
8983b5899c4f16c5448caf070638139a9cf0b6520d42a544328ff5754eae280b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for pharmguide-mcp 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.