PubMed MCP Server

Created By
pipethedeva year ago
Overview

what is PubMed MCP Server?

The PubMed MCP Server is a tool that enables AI assistants to search, access, and analyze PubMed articles through a simple Model Context Protocol (MCP) interface, bridging AI models with a vast repository of biomedical literature.

how to use PubMed MCP Server?

To use the PubMed MCP Server, install it via the Smithery CLI, clone the repository, install dependencies, and start the server using Python. You can then configure it to work with various AI clients like Claude Desktop or Cursor.

key features of PubMed MCP Server?

  • 🔎 Paper Search: Query PubMed articles with keywords or advanced search.
  • 🚀 Efficient Retrieval: Fast access to paper metadata.
  • 📊 Metadata Access: Retrieve detailed metadata for specific papers.
  • 📄 Paper Access: Attempt to download full-text PDF content.
  • 🧠 Deep Analysis: Perform comprehensive analysis of papers.
  • 📝 Research Prompts: A set of specialized prompts for paper analysis.

use cases of PubMed MCP Server?

  1. Searching for recent biomedical research papers.
  2. Retrieving detailed metadata for specific articles.
  3. Performing deep analysis on scientific literature.

FAQ from PubMed MCP Server?

  • Can I use PubMed MCP Server for all types of research?

Yes! It is designed for biomedical research and can access a wide range of articles in this field.

  • Is there a cost to use the PubMed MCP Server?

No! The PubMed MCP Server is free to use for research purposes.

  • What are the prerequisites for using the PubMed MCP Server?

You need Python 3.10+ and the FastMCP library installed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pipethedev
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago