PubMed MCP

Created By
grlla year ago
A MCP server for PubMed data
Overview

what is PubMed MCP?

PubMed MCP is a server that allows users to search and fetch articles from the PubMed database, which contains over 35 million citations for biomedical literature.

how to use PubMed MCP?

To use PubMed MCP, you need to add specific configurations to your claude_desktop_config.json file, ensuring that the necessary command and environment variables are set up correctly.

key features of PubMed MCP?

  • Search and fetch articles from the extensive PubMed database.
  • Utilizes the pubmedclient Python package for efficient operations.
  • Supports integration with the Claude desktop application.

use cases of PubMed MCP?

  1. Researchers can quickly access relevant biomedical literature for their studies.
  2. Students can find articles for their assignments and projects.
  3. Healthcare professionals can stay updated with the latest research findings.

FAQ from PubMed MCP?

  • What is PubMed?

PubMed is a free search engine accessing primarily the MEDLINE database of references and abstracts on life sciences and biomedical topics.

  • How do I install the required components?

Ensure that the 'uv' command is installed on your system and that 'uvx' is available in your PATH.

  • Can I use PubMed MCP for all types of articles?

Yes, PubMed MCP provides access to a wide range of biomedical literature, including articles from life science journals and online books.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
grll
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

3 hours ago
Gpt Scrambler

2 days ago