MCP server for PubMed — enables Claude to interact with PubMed data and workflows.
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
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
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
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
Strong directory entry: PubMed surfaces stars and publisher context so we could sanity-check maintenance before adopting.
PubMed reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated PubMed against two servers with overlapping tools; this profile had the clearer scope statement.
We evaluated PubMed against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: PubMed is the kind of server we cite when onboarding engineers to host + tool permissions.
PubMed has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
PubMed is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We wired PubMed into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, PubMed benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Useful MCP listing: PubMed is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 73
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"pubmed": {
"type": "http",
"url": "https://pubmed.mcp.claude.com/mcp"
}
}
}PubMed MCP server for Claude integration. Enables AI assistants to interact with PubMed data and workflows.
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.
Add the following to your .mcp.json file to connect Claude to PubMed. No local installation required — this is a remote HTTP server.
README content is unavailable from source data for this server.
Open GitHub repository →Time estimate: 20-40 minutes including configuration and testing
Prerequisites
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ 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.