
PubMed
STDIOMCP server providing PubMed biomedical literature database access for AI and research tools.
MCP server providing PubMed biomedical literature database access for AI and research tools.
A production-grade Model Context Protocol (MCP) server that empowers AI agents and research tools with comprehensive access to PubMed. Enables advanced, automated workflows for searching, retrieving, analyzing, and visualizing biomedical and scientific literature via NCBI E-utilities.
Built on the cyanheads/mcp-ts-template
, this server follows a modular architecture with robust error handling, logging, and security features.
This server equips your AI with specialized tools to interact with PubMed:
Tool Name | Description | Example |
---|---|---|
pubmed_search_articles | Searches PubMed for articles based on your query. | View Example |
pubmed_fetch_contents | Retrieves detailed information for PubMed articles. | View Example |
pubmed_article_connections | Finds related articles (cited by, similar, references) or formats citations for a PMID. | Ex. 1, Ex. 2 |
pubmed_research_agent | Generates a standardized JSON research plan outline from component details. | View Example |
pubmed_generate_chart | Generates a chart image (PNG) from given input data. | View Examples |
Overview | Features | Installation |
---|---|---|
Configuration | Project Structure | |
Tools | Development & Testing | License |
The PubMed MCP Server acts as a bridge, allowing applications (MCP Clients) that understand the Model Context Protocol (MCP) – like advanced AI assistants (LLMs), IDE extensions, or custom research tools – to interact directly and efficiently with PubMed's vast biomedical literature database.
Instead of complex API integration or manual searches, your tools can leverage this server to:
Built on the robust mcp-ts-template
, this server provides a standardized, secure, and efficient way to expose PubMed functionality via the MCP standard. It achieves this by integrating with NCBI's E-utilities API, ensuring compliance with rate limits and providing comprehensive error handling.
Developer Note: This repository includes a .clinerules file that serves as a developer cheat sheet for your LLM coding agent with quick reference for the codebase patterns, file locations, and code snippets.
Leverages the robust utilities provided by the mcp-ts-template
:
McpError
), and automatic logging.dotenv
) with comprehensive validation using Zod.zod
for schema validation and custom sanitization logic.AsyncLocalStorage
.Dockerfile
for creating small, secure production images with native dependency support.Add the following to your MCP client's configuration file (e.g., cline_mcp_settings.json
).
This configuration uses npx
to run the server, which will automatically install the package if not already present.
All environment variables are optional, but recommended for production use. NCBI API key is recommended to avoid rate limiting issues.
{ "mcpServers": { "pubmed-mcp-server": { "command": "npx", "args": ["@cyanheads/pubmed-mcp-server"], "env": { "MCP_LOG_LEVEL": "debug", "MCP_TRANSPORT_TYPE": "http", "MCP_HTTP_PORT": "3017", "NCBI_API_KEY": "YOUR_NCBI_API_KEY_HERE" } } } }
npm install @cyanheads/pubmed-mcp-server
git clone https://github.com/cyanheads/pubmed-mcp-server.git cd pubmed-mcp-server
npm install
npm run build
Configure the server using environment variables. For local development, these can be set in a .env
file at the project root or directly in your environment. Otherwise, you can set them in your MCP client configuration as shown above.
Variable | Description | Default |
---|---|---|
MCP_TRANSPORT_TYPE | Transport mechanism: stdio or http . | stdio |
MCP_HTTP_PORT | Port for the HTTP server (if MCP_TRANSPORT_TYPE=http ). | 3017 |
MCP_HTTP_HOST | Host address for the HTTP server (if MCP_TRANSPORT_TYPE=http ). | 127.0.0.1 |
MCP_ALLOWED_ORIGINS | Comma-separated list of allowed origins for CORS (if MCP_TRANSPORT_TYPE=http ). | (none) |
MCP_LOG_LEVEL | Logging level (debug , info , notice , warning , error , crit , alert , emerg ). | debug |
MCP_AUTH_MODE | Authentication mode for HTTP: jwt or oauth . | jwt |
MCP_AUTH_SECRET_KEY | Required for jwt auth. Minimum 32-character secret key for JWT authentication. | (none) |
NCBI_API_KEY | Recommended. Your NCBI API Key for higher rate limits and reliable access. | (none) |
LOGS_DIR | Directory for log file storage. | logs/ |
NODE_ENV | Runtime environment (development , production ). | development |
The codebase follows a modular structure within the src/
directory:
src/
├── index.ts # Entry point: Initializes and starts the server
├── config/ # Configuration loading (env vars, package info)
│ └── index.ts
├── mcp-server/ # Core MCP server logic and capability registration
│ ├── server.ts # Server setup, capability registration
│ ├── transports/ # Transport handling (stdio, http)
│ └── tools/ # MCP Tool implementations (subdirs per tool)
├── services/ # External service integrations
│ └── NCBI/ # NCBI E-utilities API client and parsing
├── types-global/ # Shared TypeScript type definitions
└── utils/ # Common utility functions (logger, error handler, etc.)
For a detailed file tree, run npm run tree
or see docs/tree.md.
The PubMed MCP Server provides a comprehensive suite of tools for biomedical literature research, callable via the Model Context Protocol.
Tool Name | Description | Key Arguments |
---|---|---|
pubmed_search_articles | Searches PubMed for articles using queries, filters, and date ranges. | queryTerm , maxResults? , sortBy? , dateRange? , filterByPublicationTypes? , fetchBriefSummaries? |
pubmed_fetch_contents | Fetches detailed article information using PMIDs or search history. | pmids? , queryKey? , webEnv? , detailLevel? , includeMeshTerms? , includeGrantInfo? |
pubmed_article_connections | Finds related articles, citations, and references for a given PMID. | sourcePmid , relationshipType? , maxRelatedResults? , citationStyles? |
pubmed_research_agent | Generates structured research plans with literature search strategies. | project_title_suggestion , primary_research_goal , research_keywords , organism_focus? , p1_* , etc. |
pubmed_generate_chart | Creates customizable PNG charts from structured publication data. | chartType , dataValues , xField , yField , title? , seriesField? , sizeField? |
Note: All tools support comprehensive error handling and return structured JSON responses.
Comprehensive usage examples for each tool are available in the examples/
directory.
pubmed_search_articles
: View Examplepubmed_fetch_contents
: View Examplepubmed_article_connections
: Ex. 1, Ex. 2pubmed_research_agent
: View Examplepubmed_generate_chart
: View Examples# Build the project (compile TS to JS in dist/ and make executable) npm run build # Clean build artifacts npm run clean # Clean build artifacts and then rebuild the project npm run rebuild # Lint the codebase npm run lint # Format code with Prettier npm run format # Generate a file tree representation for documentation npm run tree
# Start the server using stdio (default) npm start # Or explicitly: npm run start:stdio # Start the server using HTTP transport npm run start:http # Test the server locally using the MCP inspector tool (stdio transport) npm run inspector # Test the server locally using the MCP inspector tool (http transport) npm run inspector:http
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.