PubMed MCP
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_abstractsA | Search abstracts on PubMed database based on the request parameters. |
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 confusion between tools. The single tool is inherently distinct.
There is only one tool, so naming consistency is not a concern. The name 'search_abstracts' follows a clear verb_noun pattern.
A single tool for a comprehensive biomedical database like PubMed feels significantly under-scoped. Users would benefit from additional tools for specific operations (e.g., fetching full details, filtering by fields).
The server lacks tools for specialized queries, structured data retrieval, or pagination. While the single tool returns rich data, it does not cover common PubMed operations like fetching a specific article by ID or searching by author/journal.