Health Gorilla MCP Server for LlamaIndex 12 tools — connect in under 2 minutes
LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Health Gorilla as an MCP tool provider through the Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI
async def main():
# Your Vinkius token — get it at cloud.vinkius.com
mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
mcp_tool_spec = McpToolSpec(client=mcp_client)
tools = await mcp_tool_spec.to_tool_list_async()
agent = FunctionAgent(
tools=tools,
llm=OpenAI(model="gpt-4o"),
system_prompt=(
"You are an assistant with access to Health Gorilla. "
"You have 12 tools available."
),
)
response = await agent.run(
"What tools are available in Health Gorilla?"
)
print(response)
asyncio.run(main())
* 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 Health Gorilla MCP Server
Connect Health Gorilla to any AI agent via MCP.
How to Connect Health Gorilla to LlamaIndex via MCP
Follow these steps to integrate the Health Gorilla MCP Server with LlamaIndex.
Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Run the agent
Save to agent.py and run: python agent.py
Explore tools
The agent discovers 12 tools from Health Gorilla
Why Use LlamaIndex with the Health Gorilla MCP Server
LlamaIndex provides unique advantages when paired with Health Gorilla through the Model Context Protocol.
Data-first architecture: LlamaIndex agents combine Health Gorilla tool responses with indexed documents for comprehensive, grounded answers
Query pipeline framework lets you chain Health Gorilla tool calls with transformations, filters, and re-rankers in a typed pipeline
Multi-source reasoning: agents can query Health Gorilla, a vector store, and a SQL database in a single turn and synthesize results
Observability integrations show exactly what Health Gorilla tools were called, what data was returned, and how it influenced the final answer
Health Gorilla + LlamaIndex Use Cases
Practical scenarios where LlamaIndex combined with the Health Gorilla MCP Server delivers measurable value.
Hybrid search: combine Health Gorilla real-time data with embedded document indexes for answers that are both current and comprehensive
Data enrichment: query Health Gorilla to augment indexed data with live information before generating user-facing responses
Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Health Gorilla for fresh data
Analytical workflows: chain Health Gorilla queries with LlamaIndex's data connectors to build multi-source analytical reports
Health Gorilla MCP Tools for LlamaIndex (12)
These 12 tools become available when you connect Health Gorilla to LlamaIndex via MCP:
cancel_lab_order
Orders in "received" or "pending" status can typically be cancelled. Orders already in "collected" or "testing" status cannot be cancelled and require lab notification. A cancellation reason is recommended for audit purposes. Use this when an order was submitted in error, the patient refused testing, or clinical circumstances have changed. Cancel a pending laboratory order
create_patient_record
Required fields: first name, last name, date of birth, and gender. Optional: address, phone, email, MRN (Medical Record Number), and insurance information. Use this to register a new patient before submitting lab orders. Returns the patient ID for use in subsequent order submissions. Create a new patient record in the Health Gorilla system
get_lab_results
Returns structured data suitable for EHR integration or clinical review. Results include timestamp of completion, pathologist sign-off (if applicable), and any critical value notifications. Use this to review patient results, identify abnormal values, or populate EHR records. Retrieve detailed laboratory results for a specific completed order
get_order_status
Status values include: "received", "in_progress", "collected", "testing", "completed", "cancelled". Returns order details, specimen collection status, lab processing information, and estimated completion time. Use this to track order progress, update patients on result timelines, or verify completion status. Check the current status of a submitted laboratory order
get_patient_demographics
Returns name, DOB, gender, contact information, MRN, and registration date. Use this to verify patient identity before order submission or to review patient registration details. Get demographic information for a registered patient
get_provider_details
Use this to verify provider credentials, obtain contact information for referrals, or confirm network participation before ordering tests. Get detailed information about a specific healthcare provider
list_orders
Optional filters: status (e.g., "pending", "completed", "cancelled") and patient_id. Each order includes order ID, patient name, test names, status, order date, and performing lab. Use this to review recent orders, track pending work, or audit ordering patterns. List laboratory orders with optional filtering by status or patient
list_patient_results
Includes test names, values, dates, and order references. Useful for trend analysis and longitudinal patient monitoring (e.g., tracking HbA1c over time, monitoring lipid panels). Use this for chronic disease management, preventive care follow-up, or comprehensive patient history review. List all laboratory results for a specific patient across all orders
match_patient
Returns match score and potential matches. Use this before creating new orders to avoid duplicate patient records and ensure results are attributed to the correct patient. Critical for data integrity in healthcare systems. Match a patient against existing records in the Health Gorilla network
search_lab_tests
Returns test names, LOINC codes, categories (chemistry, hematology, microbiology, etc.), turnaround times, and performing laboratory information. Use this to find the correct test codes (LOINC/CPT) before submitting orders, explore available diagnostic options, or verify test availability. Optional query parameter accepts free-text search. Optional category parameter filters by test type. Search the Health Gorilla lab test catalog by name, LOINC code, or category
search_providers
Results include provider name, specialty, NPI number, location, and contact information. Use this to find ordering providers, verify network participation, or locate specialists in a specific area. Optional filters: specialty (e.g., "Internal Medicine", "Cardiology") and location. Search for healthcare providers in the Health Gorilla network
submit_lab_order
The order includes patient demographics, ordering provider information, requested tests (LOINC/CPT codes), clinical indication/diagnosis (ICD-10 codes), and specimen collection details. Returns an order ID for tracking status and retrieving results. Use this to place lab orders electronically without manual paperwork. Supported test types include chemistry panels, CBC, metabolic panels, infectious disease testing, genetic testing, and radiology orders. The order is routed to the appropriate performing laboratory (Quest, LabCorp, etc.). Submit a new laboratory or radiology order through the Health Gorilla diagnostic network
Troubleshooting Health Gorilla MCP Server with LlamaIndex
Common issues when connecting Health Gorilla to LlamaIndex through the Vinkius, and how to resolve them.
BasicMCPClient not found
pip install llama-index-tools-mcpHealth Gorilla + LlamaIndex FAQ
Common questions about integrating Health Gorilla MCP Server with LlamaIndex.
How does LlamaIndex connect to MCP servers?
Can I combine MCP tools with vector stores?
Does LlamaIndex support async MCP calls?
Connect Health Gorilla with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Health Gorilla to LlamaIndex
Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.