PubMed▌
by PubMed
MCP server for PubMed — enables Claude to interact with PubMed data and workflows.
PubMed MCP server that connects Claude to PubMed through the Model Context Protocol. Configured as a HTTP server at https://pubmed.mcp.claude.com/mcp. Available in 1 Anthropic knowledge-work plugin(s): bio-research.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Teams using PubMed
- / Automating PubMed workflows with AI
- / Claude integration with PubMed
capabilities
- / Access PubMed data from Claude
- / Perform PubMed operations via AI
- / Model Context Protocol integration
what it does
PubMed MCP server for Claude integration. Enables AI assistants to interact with PubMed data and workflows.
about
PubMed is an official MCP server included in Anthropic's knowledge-work-plugins repository. It enables Claude to interact with PubMed through the Model Context Protocol. Protocol: HTTP. Endpoint: https://pubmed.mcp.claude.com/mcp. Used in plugins: bio-research.
how to install
Add the following to your .mcp.json file to connect Claude to PubMed. No local installation required — this is a remote HTTP server.
license
Proprietary
PubMed is a proprietary service. Usage is subject to PubMed's terms of service.
readme
README content is unavailable from source data for this server.
Open GitHub repositoryFAQ
- What is the PubMed MCP server?
- PubMed is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for PubMed?
- This profile displays 73 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Web Research & Information Gathering
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Content Monitoring & Alerts
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Data Extraction & Aggregation
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
API-less Integration
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Implementation Guide▌
Prerequisites
- ›Claude Desktop or Cursor with MCP support
- ›Understanding of web scraping ethics and robots.txt
- ›Rate limiting awareness to avoid overwhelming target sites
- ›Knowledge of legal restrictions on data collection
Time Estimate
20-40 minutes including configuration and testing
Installation Steps
- 1.Install web automation MCP server via npm or pip
- 2.Configure allowed domains and rate limits in MCP config
- 3.Test with simple fetch: 'Get content from example.com'
- 4.Progress to extraction: 'Extract all product prices from this page'
- 5.Set up monitoring: 'Check this URL daily for changes'
- 6.Parse structured data: 'Create CSV from this table'
- 7.Respect robots.txt and rate limits always
Troubleshooting
- ⚠403 Forbidden: Website blocks bots—respect their wishes, use official API instead
- ⚠Rate limit errors: Slow down requests, add delays between fetches
- ⚠Stale data: Target site changed HTML structure—update selectors
- ⚠Timeout errors: Site is slow or blocking—increase timeout, try different user agent
- ⚠JavaScript-rendered content: Use headless browser MCP servers for dynamic sites
Best Practices▌
✓ Do
- +Check robots.txt and respect crawl rules
- +Rate limit requests: 1-2 requests/second maximum
- +Use official APIs when available instead of scraping
- +Identify your bot with descriptive user agent
- +Cache results to minimize repeated requests
- +Handle errors gracefully with retries and fallbacks
- +Validate extracted data for accuracy
✗ Don't
- −Don't scrape sites that explicitly forbid it (robots.txt, ToS)
- −Don't overwhelm servers with rapid requests—use rate limiting
- −Don't scrape personal data without consent and legal basis
- −Don't ignore copyright on extracted content
- −Don't assume HTML structure is stable—handle changes
- −Don't use scraped data for commercial purposes without permission
💡 Pro Tips
- ★Use CSS selectors or XPath for robust data extraction
- ★Set up monitoring alerts for extraction failures (structure changed)
- ★Implement exponential backoff for retries on failures
- ★Store raw HTML for reprocessing if extraction logic changes
- ★Combine with data analysis tools for insights from extracted data
- ★Consider using official APIs or RSS feeds as more stable alternatives
Technical Details▌
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
- HTTP/HTTPS
- WebSocket (for real-time sites)
- Puppeteer/Playwright (for JavaScript sites)
Compatibility
- Static HTML sites
- JavaScript-rendered SPAs (with headless browser)
- REST APIs
- GraphQL endpoints
When to Use This▌
✓ Use When
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid When
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.
Integration▌
- →Scheduled monitoring with change detection
- →Multi-source data aggregation pipelines
- →Fallback to web scraping when API rate limits hit
- →Headless browser for JavaScript-heavy sites
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.7★★★★★73 reviews- ★★★★★Omar Robinson· Dec 28, 2024
Strong directory entry: PubMed surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Ganesh Mohane· Dec 24, 2024
PubMed reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Omar Ndlovu· Dec 24, 2024
We evaluated PubMed against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Omar Gonzalez· Dec 20, 2024
We evaluated PubMed against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Nia Gupta· Dec 16, 2024
Useful MCP listing: PubMed is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Nia Anderson· Dec 12, 2024
PubMed has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Advait Harris· Dec 8, 2024
PubMed is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Kiara Kim· Dec 4, 2024
We wired PubMed into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Kaira Martin· Nov 23, 2024
According to our notes, PubMed benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Soo Garcia· Nov 19, 2024
Useful MCP listing: PubMed is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 73