pubmed-search-mcp
Related Servers
Alternatives to pubmed-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables coding agents to search academic papers, ingest full-text PDFs, extract structured details, and manage citations in literature research workflows.31MIT
- AlicenseAqualityCmaintenanceUnified MCP server for scientific literature search and extraction, integrating databases like Scopus, OpenAlex, Semantic Scholar, and Unpaywall to enable AI agents to discover papers, track citations, and analyze content.27MIT
- FlicenseAqualityDmaintenanceAI-powered research assistant MCP server for searching academic papers and answering research questions with DOI citations.3-
- FlicenseNot gradedqualityDmaintenanceAn advanced scholarly research MCP server that enables AI assistants to discover, fetch, process, and manage academic papers across multiple sources like arXiv, PubMed, and Semantic Scholar, with capabilities for summarization, citation analysis, and concept relationship extraction.2-
- AlicenseAqualityDmaintenanceMCP server enabling AI agents to search and retrieve scientific papers, citations, and author profiles from Crossref, OpenAlex, and Semantic Scholar with no API keys required.519 PyPI3MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for AI-assisted research: paper ingestion, semantic search, citation graph traversal, cross-domain knowledge synthesis, and workflow automation.MIT
TDQS
Scored across 41 tools
The set contains several overlapping clusters: unified_search vs generate_search_queries/analyze_search_query, four citation-exploration tools (find_related_articles, find_citing_articles, get_article_references, build_citation_tree), and multiple fulltext/institutional-access tools (get_fulltext, diagnose_institutional_access, get_institutional_link, configure_institutional_access, test_institutional_access). Descriptions are unusually detailed and cross-reference each other, which mitigates confusion, but an agent must still inspect descriptions carefully to avoid misselection.
All 41 tools use snake_case with a consistent verb_noun or verb_phrase pattern (search_gene, get_fulltext, build_citation_tree, save_literature_notes, etc.). There is no camelCase or mixed casing, and the single adjective-first tool unified_search does not meaningfully break the predictable convention.
With 41 tools, this server is far beyond the 3-15 sweet spot and includes many specialized helpers (seven pipeline tools, five institutional-access tools, three gene tools, three compound tools, session/artifact readers, and image/chronicle tools). Each may have a distinct purpose, but the sheer count makes the surface heavy and raises selection cost for an agent.
The surface covers search and discovery, citation networks, fulltext retrieval, export, note-saving, pipeline lifecycle (save/list/load/delete/schedule/unschedule/history), persistent research chronicles, gene/compound lookup, biomedical image search, and institutional access. No obvious lifecycle gaps are present, and overwrite/upsert semantics handle missing update operations.