Truepill MCP for AI. Pulling Patient Histories from Conversation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Truepill is an MCP Server for managing patient records and pharmacy operations. It lets your AI agent interact with core healthcare functions—creating new patients, finding existing ones by demographics, updating profiles, and pulling complete prescription histories (Rx).
Use it to pull specific metadata like NDC codes or monitor real-time system events directly from conversation.
What AI agents can do with Truepill Automation
Create patient
Builds an entirely new patient record and returns the unique token for that profile.
Find patient
Searches the database using demographic criteria (like name or DOB) to locate a patient's existing record.
Get patient prescriptions
Pulls a complete list of every prescription ever filled or ordered for a given patient's token.
The server creates new patient records using create_patient and allows updates to non-critical fields with update_patient.
You can locate a patient's record token simply by giving the agent name, date of birth, or zip code using find_patient.
Once you have a token, get_patient pulls all demographic and contact information for that specific person.
The agent calls get_patient_prescriptions to pull every prescription associated with a patient's token.
Using get_prescription, you can drill down into specific details about one medication, like the NDC or how many refills are left.
The get_webhook_events tool retrieves real-time status changes from the pharmacy lifecycle, such as shipment confirmations.
Ask an AI about this
Waiting for input…
What AI agents can do with Truepill MCP Server: 7 Tools for Pharmacy Data Management
These tools let your AI client perform specific actions on patient records—creating profiles, fetching history, or monitoring system changes.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Truepill on VinkiusCreate Patient
Builds an entirely new patient record and returns the unique token for that profile.
Find Patient
Searches the database using demographic criteria (like name or DOB) to locate a...
Get Patient Prescriptions
Pulls a complete list of every prescription ever filled or ordered for a given...
Get Patient
Retrieves all core profile details for a patient when you provide their unique token.
Get Prescription
Fetches detailed metadata for one specific medication, including prescriber details...
Get Webhook Events
Grabs recent system status changes from the pharmacy, like order shipments or transfers.
Update Patient
Modifies non-critical information on an existing patient record, such as their phone number or email address.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Truepill integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Truepill, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Truepill. 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 7 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually pulling patient data means jumping between four different tabs and systems., Solved with Vinkius AI Gateway
Right now, checking a patient's full status is painful. You open the main EHR for demographics; you switch to the Rx tab to see active meds; then you jump to the orders log just to confirm shipping. It’s copy-pasting tokens and running separate lookups—it takes time and introduces errors.
With this MCP server, your agent does it all in one prompt. You tell it what you need ('Show me everything about Mary Smith'), and it handles the multi-step process: `find_patient` for the ID, then runs `get_patient`, followed by `get_patient_prescriptions`. It delivers a compiled answer.
Truepill MCP Server gives you immediate visibility into system changes with get_webhook_events.
Historically, if an order was shipped or transferred from one facility to another, that status update might sit in a separate notification queue. You had to remember to check the 'Activity Log' tab—a step people often skipped under pressure.
Now, you simply ask your agent for recent events. It runs `get_webhook_events` and pulls structured data on shipment confirmations, order statuses, or transfers right into the conversation flow. That eliminates manual checking entirely.
What your AI can actually do with this
Truepill lets your AI agent handle all the grunt work of patient records and pharmacy operations. You connect it to any AI client, and instead of jumping between a bunch of dashboards, your agent just calls what's needed. It’s built for people who need fast, structured access to critical health data—period.
Managing Patient Profiles
You can start by building an entirely new patient file using create_patient; the system returns that unique token you need right away. Need to find a person first? You don't have to guess; your agent uses find_patient to search the database just by name, date of birth, or zip code to locate their existing record.
Once you get that patient token, get_patient pulls all core profile details—everything from demographics to contact info—for that specific person.
Keep the file current with modifications: if a client changes their phone number or email address, your agent uses update_patient to change those non-critical fields on an existing record. You never gotta manually type anything; it just gets updated right there.
Rx History and Drug Details
The server gives you full visibility into a patient's medication history. To pull every single prescription ever filled or ordered for any given person, your agent calls get_patient_prescriptions using their token. You get a complete list of everything associated with that file.
If you need to drill down on just one drug—say, figuring out the NDC code or checking how many refills are left—you use get_prescription. This tool fetches detailed metadata for one specific medication, including exactly who prescribed it and its current refill count. It’s like having a deep dive into the drug file itself.
System Monitoring
The system keeps you in the loop on everything happening at the pharmacy. When orders ship or records transfer status, your agent calls get_webhook_events. This grabs recent system status changes directly from the pharmacy lifecycle, letting you know about major events like shipment confirmations without having to refresh any screens.
How It Works
The whole process works by giving your AI client access to specific tools. You never write API calls; you just tell your agent what you need—like "Find the record for Jane Smith born 01/01/1985"—and it handles calling find_patient. If that's successful, and you want her full profile, it immediately uses that token to call get_patient, keeping everything fast.
It’s all about chaining those operations together without human intervention.
019ea60c-8f93-703d-867c-a8bdb72ae336 
Here's how it actually works
The bottom line is: you talk to your AI agent, and it handles the sequence of API calls needed to build the answer for you.
First, subscribe to this server and enter your Truepill API Key into your AI client.
Next, prompt your agent with a request (e.g., 'Find the patient for John Doe'). The agent executes find_patient to get a token.
Finally, use that token in subsequent calls—like running get_patient_prescriptions — to pull all required data.
Who is this actually for?
This is for anyone who spends time in healthcare operations but hates jumping between three different screens just to pull one patient's history. It’s for the clinical staff, the billing department, and developers who need reliable, structured access to core patient data without building complex scripts.
A nurse uses this to quickly look up a patient's full history or check current medication statuses during an urgent consultation.
An ops manager relies on the agent to monitor system events and track bulk orders, ensuring nothing falls through the cracks without manual dashboard checking.
A developer uses this directly in their code editor to test data structures and verify API calls before deploying a new feature.
What Changes When You Connect
Real-time status updates: You don't have to manually check the dashboard for order changes. Running get_webhook_events lets your agent pull immediate notifications about shipment or transfer status changes.
Quick patient identification: Forget tedious searches. Use find_patient with just a name and DOB, and the agent returns the needed token instantly. This saves minutes per lookup.
Deep prescription dives: Need to know if a drug has refills left? Running get_prescription provides metadata like NDC codes and refill counts without needing a separate billing tool.
Full profile access: Once you find the patient, get_patient_prescriptions pulls the entire history in one go. You get everything—not just the last thing they filled.
Efficient data entry: If a patient moves or changes their phone number, you use update_patient. It handles changing contact details without requiring manual form submission.
See it in action
Checking a complex medication history
A nurse needs to check if a patient is allergic or has taken drug X before. They ask their agent: 'Show me all prescriptions for pt_123.' The agent runs get_patient_prescriptions and then uses get_prescription on key items, pulling the full history in minutes.
Admitting a new patient
A staff member has basic demographic data for a walk-in. They ask their agent to 'Create a record for Jane Doe.' The agent runs create_patient, gets the token, and confirms it's ready for use in other systems.
Tracking an outgoing order
The pharmacy manager needs to know if today's large transfer shipment was successfully logged. They prompt their agent: 'What are the recent system events?' The agent executes get_webhook_events and gives them a list of confirmed status changes.
Updating contact info for an old record
A patient calls in with a new address, but the records are old. Instead of manually finding the profile, they ask their agent to 'Update John Smith's phone number.' The agent uses update_patient and confirms the change.
The honest tradeoffs
Trying to get details without a token
A user tries to prompt: 'What are John Doe's prescriptions?' The agent fails because it needs an identifier first. It can't just guess.
First, use find_patient with demographics (name/DOB) to get the patient token. Then, run get_patient_prescriptions using that specific token.
Calling update on unchangeable fields
A user tries to use update_patient and passes a request to change the date of birth (DOB). The tool will fail because DOB is locked.
Only use update_patient for mutable data like phone, email, or address. Never try to modify core identifying information through this tool.
Overlooking event monitoring
Assuming a prescription status change is logged somewhere else, the user misses critical real-time alerts.
To stay current on system changes (like a filled order or transfer), always run get_webhook_events to check the latest pharmacy lifecycle updates.
When It Fits, When It Doesn't
Use this server if your primary need is structured, conversational access to patient demographic data and prescription history. The clear separation between lookup (find_patient) and retrieval (get_patient, get_patient_prescriptions) forces a reliable workflow: Find -> Get Token -> Act/Read Data. This works perfectly when you need the AI agent to perform sequenced actions.
Don't use this if your core problem involves billing codes, insurance verification, or complex drug-interaction analysis that requires external knowledge bases outside of Truepill’s scope. If your system needs advanced financial transaction logging, look at a dedicated financial API server instead.
Questions you might have
How do I start using get_patient_prescriptions with Truepill? +
You first need a patient's token. Use find_patient to locate the ID, then pass that token directly into the agent's call for get_patient_prescriptions. It returns every filled prescription.
Can I update a patient's address using update_patient? +
Yes. You use update_patient and specify the new address details. Just remember that core identifiers like DOB or last name cannot be changed with this tool.
What is the difference between get_patient and find_patient? +
find_patient runs a search using demographics (name, zip). It gives you a token. get_patient takes that specific token to pull all the associated profile data.
Does Truepill help me monitor order shipments? +
Yes. You use the get_webhook_events tool. This retrieves recent pharmacy events, including status changes for orders and transfers.
How do I start with `create_patient` to onboard a new patient record? +
The create_patient tool generates a unique patient token. This token is essential because you must use it for all subsequent actions, like retrieving full profiles or adding prescriptions.
What specific information does the `get_prescription` tool retrieve? +
This tool pulls deep metadata about one single prescription instance. You'll get details on the prescriber, NDC codes, and how many refills are available for that item.
If I run `get_webhook_events`, what types of pharmacy lifecycle changes can I track? +
You monitor various system events using this tool. It tracks key stages like prescription notifications (NOTIFY_RX), new orders, shipments, or patient record transfers.
Are there any fields in `update_patient` that are read-only? +
Yes, while you can update contact details like address and phone number, certain required identifiers—specifically the date of birth or last name—cannot be changed using this endpoint.
Can I search for a patient without having their specific patient token? +
Yes. You can use the find_patient tool to search by first name, last name, date of birth, or zip code to locate the correct record.
How do I check the status of all medications assigned to a patient? +
Use the get_patient_prescriptions tool with the patient's token. It will return a list of all prescriptions, their current status, and whether they are fillable.
Is it possible to update a patient's date of birth if it was entered incorrectly? +
No. The update_patient tool only allows modifications to non-required fields like address, phone, and email. Required identity fields like DOB cannot be changed via this tool.
We've already built the connector for Truepill. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 7 tools are live and waiting.
You're up and running in seconds.
Gemini 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.
Built, hosted, and secured by Vinkius. You just connect and go.