Vinkius
PMC Open Access (PubMed Central) logo
Vinkius
Vinkius runs on Google ADK

How to Use the PMC Open Access (PubMed Central) MCP in Google ADK

Feed PMC Open Access (PubMed Central) metadata directly into Gemini's million-token context using Google ADK.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

PMC Open Access (PubMed Central) MCP on Cursor AI Code Editor MCP Client PMC Open Access (PubMed Central) MCP on Claude Desktop App MCP Integration PMC Open Access (PubMed Central) MCP on OpenAI Agents SDK MCP Compatible PMC Open Access (PubMed Central) MCP on Visual Studio Code MCP Extension Client PMC Open Access (PubMed Central) MCP on GitHub Copilot AI Agent MCP Integration PMC Open Access (PubMed Central) MCP on Google Gemini AI MCP Integration PMC Open Access (PubMed Central) MCP on Lovable AI Development MCP Client PMC Open Access (PubMed Central) MCP on Mistral AI Agents MCP Compatible PMC Open Access (PubMed Central) MCP on Amazon AWS Bedrock MCP Support
MCP Servers — Included with Plan
Vinkius runs on Google ADK

Connect PMC Open Access (PubMed Central) MCP to Google ADK

Create your Vinkius account to connect PMC Open Access (PubMed Central) to Google ADK — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Key Capabilities

Long-context research with Google ADK

The `oa_discover` tool finds downloadable XML and PDF paths from the PMC Open Access Subset, sending them straight to your Google ADK agent. Because Gemini supports over a million tokens of context, your agent can ingest dozens of full-text papers found by this tool in a single turn. You initialize the toolset using `McpToolset` with the Vinkius HTTP transport params. This lets your enterprise agent fetch literature metadata and immediately run deep-reasoning chains over entire medical journals.

Syncing PMC Open Access MCP Server data to BigQuery

The `oai_list_records` tool extracts large-scale metadata records from PubMed Central using the OAI-PMH protocol. This MCP tool lets your Google ADK agent coordinate this extraction, formatting the XML payloads so they can be loaded directly into BigQuery tables for SQL analysis. You can restrict your agent's scope by passing a specific list of verbs to `tool_names`. This ensures your agent only calls `oai_list_records` and `oai_get_record`, avoiding accidental calls to administrative endpoints.

Mapping medical IDs within Gemini pipelines

The `convert_ids` tool resolves discrepancies between PMCID, PMID, and DOI formats inside your Google ADK runtime. This resolves the common issue of mismatched academic records before you feed the data into Vertex AI embedding models. Your agent runs this conversion natively during execution. By keeping ID resolution inside the MCP toolset, you prevent model hallucinations when referencing complex medical studies.

Setup guide

Set up PMC Open Access (PubMed Central) MCP in Google ADK

Prerequisites

  • Python 3.10+ installed
  • google-adk package (pip install google-adk)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Install Google ADK

    Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.

  2. 2

    Connect via SSE transport

    Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

  3. 3

    Create an LlmAgent

    Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.

  4. 4

    Run with any Gemini model

    The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with PMC Open Access (PubMed Central) tools in your ADK agent.

agent.py
from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="PMC Open Access (PubMed Central)_agent",
    model="gemini-2.0-flash",
    instruction="You have access to PMC Open Access (PubMed Central) tools via MCP.",
    tools=mcp_tools,
)

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by PMC (PubMed Central). All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about PMC Open Access (PubMed Central) MCP in Google ADK

Use `McpToolset` with `StreamableHttpServerParameters` pointing to your Vinkius URL. Pass this toolset to your `LlmAgent` to expose the medical search capabilities of the MCP Server.
Yes, the `oa_discover` tool retrieves the direct download URLs. Your Google ADK agent can fetch these files and load their contents into Gemini's massive context window for synthesis.
You pass a list of allowed tool names, like `export_citation` and `convert_ids`, to the `tool_names` parameter when setting up your `McpToolset` instance.
Yes, the server exposes `oai_list_identifiers` and `oai_list_metadata_formats`. Your agent can systematically crawl PubMed Central's repository using these standard protocols.
All queries, including PMCIDs and search terms, are handled within ephemeral V8 isolates on Vinkius. No biomedical metadata or proprietary search parameters are stored permanently, keeping your research pipeline compliant with enterprise security standards.

Start using the PMC Open Access (PubMed Central) MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 8 tools

We've already built the connector for PMC Open Access (PubMed Central). Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.