Compatible with every major AI agent and IDE
What is the PubMed Central MCP Server?
Connect your AI agent to PubMed Central (PMC), the world's premier digital archive of biomedical and life sciences journal literature. This server enables deep exploration of millions of open-access articles directly through natural conversation.
What you can do
- Advanced Search — Use
search_articlesto find PMCIDs matching complex queries, including authors, dates, and specific filters. - Full-Text Retrieval — Access complete article content in BioC XML or JSON formats using
get_bioc_articlefor deep analysis. - Citation Analysis — Track the scientific impact of research by finding articles that cite a specific PMID with
get_citing_articles. - Identifier Mapping — Seamlessly convert between PMCIDs, PMIDs, and DOIs using
convert_idsto ensure data consistency. - Metadata Harvesting — Retrieve document summaries, license information, and file locations for Open Access records via
get_article_summaryandget_oa_record.
How it works
- Subscribe to this server
- Provide your NCBI Tool Name and Email (and an optional API Key for higher rate limits)
- Start querying the global repository of medical knowledge from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Researchers & Academics — Instantly find relevant literature and extract data from full-text papers without manual downloading.
- Healthcare Professionals — Quickly verify medical facts and access the latest clinical studies directly from your workspace.
- Data Scientists — Automate the collection of biomedical datasets and citation networks for large-scale analysis.
Built-in capabilities (7)
Convert between article identifiers (PMCID, PMID, DOI)
Get metadata summaries for PMC articles
Retrieve full-text articles via the BioC API
Find PMC articles that cite a specific PubMed ID
Find citation data, license info, and file locations for OA articles
Harvest metadata via the PMC OAI-PMH Service
Search for articles in PubMed Central
Why Cursor?
Cursor's Agent mode turns PubMed Central into an in-editor superpower. Ask Cursor to generate code using live data from PubMed Central and it fetches, processes, and writes. all in a single agentic loop. 7 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
PubMed Central in Cursor
PubMed Central and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect PubMed Central to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for PubMed Central in Cursor
The PubMed Central MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 7 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
PubMed Central for Cursor
Every tool call from Cursor to the PubMed Central MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I convert a DOI or PMID into a PMCID for full-text access?
Use the convert_ids tool. Provide a comma-separated list of identifiers, and the agent will return the mapped PMCID, which is required for many other PMC retrieval tools.
Can I retrieve the actual content of an article, not just the abstract?
Yes. If the article is in the Open Access subset, use get_bioc_article with the PMCID. You can specify 'json' or 'xml' format to get the full-text sections.
How can I find which papers have cited a specific study?
Use the get_citing_articles tool by providing the PubMed ID (PMID) of the study. It will return a list of PMC articles that reference that specific work.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Tatum (Blockchain Infra)
11 toolsSimplify blockchain development with Tatum — estimate fees, track portfolios, and manage real-time webhook subscriptions across multiple chains.

Mistral AI (Frontier LLMs & Embeddings)
7 toolsManage AI inference via Mistral — execute chat completions, generate RAG embeddings, and audit frontier models.

Bing Search
8 toolsEmpower your AI agent with real-time web, image, and news search via Bing.

Mailgun (Transactional Email & Domains)
10 toolsManage email infrastructure via Mailgun — send transactional emails, monitor domain health, and audit delivery logs.
