Myvariant vs Mydisease — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Myvariant vs Mydisease
In-depth architectural comparison of the Myvariant and Mydisease MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Myvariant
Developer Tools · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Mydisease
Developer Tools · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Myvariant if you need specialized Developer Tools tools running via a local process. Choose Mydisease if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
M
Choose Myvariant when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Search aggregated human genetic-variant annotations on MyVariant.info. Accepts an rsID ("rs58991260"), an HGVS id ("chr1:g.218631822G>A"), or a fielded query ("dbnsfp.genename:CDK2", "clinvar.rcv.clinical_significance:pathogenic"). Each hit merges dbSNP, ClinVar clinical significance, CADD/dbNSFP d…
variant
Get the full merged annotation for a single human genetic variant by its HGVS id (e.g. "chr7:g.140453136A>T"). Returns annotations aggregated from dbSNP, ClinVar (pathogenicity / clinical significance), CADD and dbNSFP (deleteriousness/conservation scores), and gnomAD (population allele frequencies…
metadata
Returns MyVariant.info build metadata: total indexed variant count, available annotation sources (dbSNP, ClinVar, CADD, dbNSFP, gnomAD), and their current release/build versions.
Mydisease Tools (3)
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.…
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Myvariant is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Mydisease belongs to Developer Tools using local stdio subprocess. Select Myvariant when you need capabilities focused on developer tools and Mydisease when you require tools for developer tools.
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 associati…
metadata
Returns MyDisease.info build metadata: total disease document count, available annotation sources (MONDO, DOID, OMIM, DisGeNET, HPO, CTD), and their current release versions.