Mydisease
MyDisease.info MCP. Aggregated disease annotation from the BioThings ecosystem: MONDO/DOID/OMIM…
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http mydisease 'https://gateway.pipeworx.io/mydisease/mcp'{
"mcpServers": {
"mydisease": {
"type": "http",
"url": "https://gateway.pipeworx.io/mydisease/mcp"
}
}
}@pipeworx/mcp-mydiseaseclaude mcp add mydisease -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-mydisease@0.2.0{
"mcpServers": {
"mydisease": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-mydisease@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<your pipeworx_api_key>"
}
}
}
}Environment variables
PIPEWORX_API_KEYsecret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-mydisease
MyDisease.info MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
query | Search MyDisease.info for diseases by free-text name or fielded query. Returns matching hits, each keyed by a MONDO disease id (e.g. "MONDO:0015967") with the best-matching ontology and annotation keys. Use this to resolve a disease name to canonical ontology ids before calling the "disease" tool. Free text like "diabetes" or "asthma" works; fielded queries like "mondo.label:asthma" or "disgenet.xrefs.disease_name:..." narrow the search. |
disease | Fetch the full aggregated annotation object for a single disease id. Accepts MONDO ("MONDO:0015967"), DOID ("DOID:9351"), OMIM ("OMIM:125853") and other supported ontology ids. Returns cross-referenced data including MONDO ontology (labels, synonyms, xrefs, parents/children), gene-disease associations from DisGeNET, phenotypes from HPO, and chemical-disease relationships from CTD. Resolve a name to an id first via the "query" tool. |
metadata | Returns MyDisease.info build metadata: total disease document count, available annotation sources (MONDO, DOID, OMIM, DisGeNET, HPO, CTD), and their current release versions. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"mydisease": {
"url": "https://gateway.pipeworx.io/mydisease/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/mydisease/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/mydisease_query \
-H 'Content-Type: application/json' \
-d '{"query":"diabetes"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/mydisease_query. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"mydisease": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-mydisease"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-mydiseaseIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Mydisease data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Mydisease?
MyDisease.info MCP. Aggregated disease annotation from the BioThings ecosystem: MONDO/DOID/OMIM…
How do I install Mydisease?
It runs as a remote server. In Claude Code: claude mcp add --transport http mydisease 'https://gateway.pipeworx.io/mydisease/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Mydisease need an API key?
Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.
Is Mydisease open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Mydisease?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.