MeSH MCP
Related Servers
Alternatives to MeSH MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to look up NLM Medical Subject Headings: search descriptors by disease, drug, or concept term, fetch a descriptor's preferred label, synonyms, qualifiers, and related headings, and resolve everyday free-text terms to their canonical MeSH heading for PubMed indexing. Runs keyless via a hosted gateway endpoint or as a local stdio server.19 npmMIT
- AlicenseAqualityCmaintenanceEnables searching medical literature, clinical trials, drug information, guidelines, and medical fee schedules directly from Claude, returning only original sources and text without medical judgment.9MIT
- AlicenseCqualityDmaintenanceAllows AI assistants to search the Library of Congress Subject Headings (LCSH) through a simple API interface, making it easy to query and retrieve official subject headings and related terms.13MIT
- FlicenseNot gradedqualityCmaintenanceEnables dental research and clinical intelligence by providing tools to search PubMed, systematic reviews, verify citations, and query ClinicalTrials.gov directly from Claude Web and Claude Desktop.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to search, retrieve summaries, and explore documents from an Assay document library.7 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query authoritative medical sources such as FDA, WHO, PubMed, RxNorm, and ClinicalTrials.gov for drug information, safety data, health statistics, clinical guidelines, pediatric resources, and evidence-graded literature. Runs locally with no API keys or data leaving the machine.56 npmISC
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: search_mesh finds descriptors, get_mesh_record retrieves full cataloging details, get_mesh_qualifiers fetches allowable subheadings, and get_mesh_tree provides hierarchical context. There is no functional overlap—an agent can easily distinguish when to use each tool based on the specific metadata needed.
All tools follow a consistent verb_noun pattern with 'mesh' as a prefix: search_mesh, get_mesh_record, get_mesh_qualifiers, get_mesh_tree. The naming is perfectly uniform, using snake_case throughout with clear, descriptive action-object pairs.
Four tools is well-scoped for a MeSH lookup server, covering the essential workflow: search, retrieve full record, get qualifiers, and understand hierarchy. Each tool earns its place without redundancy, and the count is appropriate for the domain's focused purpose.
The toolset provides complete coverage for MeSH descriptor lookup and cataloging support. It includes search, full record retrieval, qualifier access, and tree hierarchy—covering the entire lifecycle from discovery to detailed metadata without any obvious gaps for the server's stated purpose.