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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pubmed_searchA | Search PubMed for articles by keyword. Returns a list of article profiles with PMID, title, authors, journal citation, and snippet. Supports date-range filters (YYYY:YYYY), publication-type filters (e.g. "clinical trial", "review"), sorting, and pagination. |
| pubmed_article_detailA | Fetch the full record of a PubMed article by its PMID. Returns title, authors with affiliations, abstract, keywords, MeSH terms, references, similar articles, publication types, full-text sources, journal info, and more. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| literature_review | Guide the LLM to conduct a structured literature review on a given topic using PubMed search and article details. |
| article_summary | Guide the LLM to provide a detailed summary of a specific PubMed article. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one for searching by keyword and the other for fetching full details by PMID. There is no overlap or ambiguity.
Both tools use the consistent 'pubmed_' prefix followed by descriptive action/noun pairs (pubmed_search, pubmed_article_detail), maintaining a clear and predictable pattern.
With only 2 tools, the server covers the essential PubMed operations (search and detail retrieval). While more advanced features could be added, this minimal set is well-scoped for basic article lookup.
The server covers the core search and detail retrieval workflow for PubMed articles. It lacks some advanced features like author-specific queries or citation networks, but it meets the primary need of searching and viewing articles.