Enhanced PubMed MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pubmedB | Enhanced PubMed search with complete abstract retrieval and PMC integration |
| get_full_abstractA | Get the complete abstract for a specific PMID |
| search_pmc_fulltextC | Search PubMed Central (PMC) for full-text open access articles |
| retrieve_pubmed_resultsB | Retrieve previously stored PubMed search results with pagination |
| list_pubmed_searchesB | List all previously stored PubMed and PMC searches |
| get_abstract_helpA | Get help and examples for using the get_full_abstract function |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Some tools have overlapping purposes: search_pubmed includes 'complete abstract retrieval', which duplicates get_full_abstract. Additionally, get_abstract_help is a helper for get_full_abstract but could cause confusion with get_full_abstract. Overall, most tools are distinct but these overlaps reduce clarity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_full_abstract, search_pubmed). The naming is predictable and readable, with no mixing of conventions.
With 6 tools, the count is well-scoped for a PubMed search and retrieval server. It covers core functionalities without being bloated or too sparse.
The server covers searching (PubMed and PMC), retrieving stored results, listing searches, and getting abstracts. A notable minor gap is the lack of a delete or clear function for stored searches/results, but the core workflows are complete.