Stanford PubMed MCP Server for CrewAIGive CrewAI instant access to 16 tools to Batch Get Articles, Get Abstract, Get Article, and more

Name: Stanford PubMed
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Connect your CrewAI agents to Stanford PubMed through Vinkius, pass the Edge URL in the `mcps` parameter and every Stanford PubMed tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Stanford PubMed MCP Server for CrewAI is a standout in the Education category — giving your AI agent 16 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Stanford PubMed Specialist",
    goal="Help users interact with Stanford PubMed effectively",
    backstory=(
        "You are an expert at leveraging Stanford PubMed tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Stanford PubMed "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 16 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Stanford PubMed MCP Server

Connect to the PubMed E-utilities API from the National Library of Medicine — the gold standard for biomedical literature search.

When paired with CrewAI, Stanford PubMed becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Stanford PubMed tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Full-Text Search — Search across 36M+ biomedical articles from MEDLINE
MeSH Vocabulary — Use Medical Subject Headings for precise, controlled-vocabulary searches
Clinical Trials — Filter specifically for clinical trial publications
Reviews & Meta-analyses — Find systematic reviews and meta-analyses
Gene Search — Search articles mentioning specific genes (TP53, BRCA1, EGFR)
Drug Search — Find articles about specific drugs and compounds
Citation Tracking — Find articles that cite a given paper
Related Articles — Use NCBI's similarity algorithm to discover related literature
Abstracts — Retrieve full structured abstracts for quick evaluation
Free Full Text — Filter for open access articles available in PubMed Central
Batch Retrieval — Fetch multiple articles by PMID in a single request

The Stanford PubMed MCP Server exposes 16 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 16 Stanford PubMed tools available for CrewAI

When CrewAI connects to Stanford PubMed through Vinkius, your AI agent gets direct access to every tool listed below — spanning pubmed, ncbi, biomedical, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

batch

Batch get articles on Stanford PubMed

Useful for building reading lists, comparing studies, or analyzing a collection of articles from a reference list. Retrieve multiple articles by PMID list

get

Get abstract on Stanford PubMed

For structured abstracts, returns all sections (Background, Methods, Results, Conclusions). Essential for quickly evaluating whether a paper is relevant without accessing the full text. Get the full abstract text of a PubMed article

get

Get article on Stanford PubMed

Returns title, all authors, journal name, publication date, volume, issue, pages, DOI, publication types, and language. Get article details by PubMed ID (PMID)

get

Get citations on Stanford PubMed

Essential for understanding an article's impact, finding follow-up studies, and tracking how findings have been built upon by other researchers. Get articles that cite a given PubMed article

get

Get related articles on Stanford PubMed

The algorithm considers title, abstract, MeSH headings, and substances to compute similarity scores. This is often more effective than keyword search for discovering relevant literature. Find related articles using NCBI similarity algorithm

Search by author on Stanford PubMed

Use "LastName FirstInitial" format for best results (e.g. "Doudna JA", "Zhang F"). Returns the author's publication list with article metadata. Find PubMed articles by author name

Search by journal on Stanford PubMed

Can be combined with a topic query. Use journal abbreviations or full names (e.g. "Nature", "N Engl J Med", "Lancet", "Cell", "Science", "JAMA", "BMJ"). Find articles published in a specific journal

Search by mesh on Stanford PubMed

MeSH terms provide precise topic classification. Examples: "Neoplasms", "Diabetes Mellitus", "Machine Learning", "Clustered Regularly Interspaced Short Palindromic Repeats", "COVID-19". Search using MeSH controlled vocabulary terms

Search clinical on Stanford PubMed

This includes Phase I-IV trials, randomized controlled trials, and clinical study reports. Essential for evidence-based medicine and systematic reviews. Search for clinical trial publications

Search drugs on Stanford PubMed

Uses the Substance Name field for precise matching. Examples: "metformin", "pembrolizumab", "remdesivir", "aspirin", "dexamethasone". Search articles mentioning specific drugs or compounds

Search free full text on Stanford PubMed

This filters to only return open access or author-deposited articles where the complete manuscript can be read for free. Essential for researchers without institutional journal subscriptions. Search for articles with free full-text available

Search genes on Stanford PubMed

Uses the Gene Name field tag for precise matching. Examples: "TP53", "BRCA1", "EGFR", "KRAS", "MYC". Can be combined with a topic query for more specific results. Search articles mentioning specific genes

Search pubmed on Stanford PubMed

Returns article titles, authors, journals, dates, DOIs, and publication types. Sort options: "relevance" (default), "date", "pub_date", "first_author", "journal". Search 36M+ biomedical articles on PubMed

Search recent on Stanford PubMed

Use this to stay up-to-date with the latest publications in your research area. Default is last 30 days. Find the most recent articles in a field

Search reviews on Stanford PubMed

These are the highest level of evidence synthesis in medicine and provide comprehensive overviews of research on a topic. Search for review articles and meta-analyses

Search trending on Stanford PubMed

This surfaces papers that are generating the most attention and engagement in the research community. Find trending articles in a subject area

Connect Stanford PubMed to CrewAI via MCP

Follow these steps to wire Stanford PubMed into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 16 tools from Stanford PubMed

Why Use CrewAI with the Stanford PubMed MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Stanford PubMed through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Stanford PubMed + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Stanford PubMed MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Stanford PubMed for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Stanford PubMed, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Stanford PubMed tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Stanford PubMed against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Stanford PubMed in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Stanford PubMed immediately.

"Find recent clinical trials for CAR-T cell therapy in lymphoma"

"Search for BRCA1 gene articles related to breast cancer prevention"

"Find free full-text systematic reviews on metformin and diabetes prevention"

Troubleshooting Stanford PubMed MCP Server with CrewAI

Common issues when connecting Stanford PubMed to CrewAI through Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Stanford PubMed + CrewAI FAQ

Common questions about integrating Stanford PubMed MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.