PubMed MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address (required by NCBI) | |
| PUBMED_API_KEY | No | Optional API key for higher rate limits |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pubmed_articlesB | Unified tool for PubMed operations: search biomedical literature, retrieve article metadata, and download PDFs. Access over 35 million citations from the world's largest biomedical database. Use the method parameter to specify the operation type: search with keywords, advanced filtered search, get detailed metadata, or download full-text PDFs when available. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool clearly handles all PubMed operations, so an agent cannot misselect between multiple options.
The single tool name 'pubmed_articles' follows a clear noun-based pattern, and since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool for a comprehensive biomedical database like PubMed is too few for the apparent scope. The tool description suggests multiple operations (search, retrieve, download), which would typically be split into distinct tools for better agent usability and clarity, making this count inappropriate.
The tool claims to cover search, retrieval, and PDF download operations, which addresses core PubMed use cases. However, the reliance on a single tool with a 'method parameter' for different operations may introduce gaps in agent handling, as it lacks dedicated tools for specific actions like filtering or metadata updates, but it is largely complete for basic workflows.