Compliance
Veeva Vault MCP connector
The Veeva Vault connector lets Claude, ChatGPT, Cursor, or any MCP client look up a Veeva Vault user record by ID, so your team can confirm who a user is without leaving the conversation.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
1 tool
How to connect
How to connect Veeva Vault to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Veeva Vault once
-
Open Connections, choose Add connection, and pick Veeva Vault.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Veeva Vault API key. One person generates a token in Veeva Vault and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Veeva Vault to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Veeva Vault to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Veeva Vault to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Veeva Vault to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Veeva Vault through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Compliance
Confirm who signed a document
When an audit trail entry only shows a user ID, ask the agent to pull the Veeva Vault user behind it and get the name and status in seconds.
-
Quality
Check a reviewer before a QA sign-off
Before accepting an approval on a batch record or SOP, confirm the Veeva Vault user who acted is still active and is the person you expected.
-
Regulatory
Identify a user on a submission record
Resolve the user IDs listed on a submission or correspondence record into real names so the history reads clearly during a review.
-
IT
Verify a Veeva Vault account exists
When someone reports they cannot get into Veeva Vault, look up their user record by ID and see whether the account is present and active.
-
HR
Check a leaver's Veeva Vault status
During offboarding, pull the departing employee's Veeva Vault user record to confirm the account shows as inactive.
-
Clinical operations
Put a name to a study record change
When a trial document shows a change made by an unfamiliar user ID, ask who that Veeva Vault user is before following up.
Try asking
- “Show the Veeva Vault user record for Priya Raman.”
- “Which Veeva Vault users belong to the Quality team?”
- “List Veeva Vault users added in the last 30 days.”
AI tools
Veeva Vault tools for your AI agents
1 tool is ready to call through Elaichi's MCP endpoint the moment you connect Veeva Vault, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Veeva Vault gets you
6 screens from the product, each doing one job for your Veeva Vault account.
The agent
Ask about Veeva Vault users in plain language.
Three starter prompts pull answers from live Veeva Vault user records.
- users
- documents
- studies
- submissions
Ask Elaichi to work across your apps.
Show the Veeva Vault user record for Priya Raman.
Which Veeva Vault users belong to the Quality team?
List Veeva Vault users added in the last 30 days.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect Veeva Vault from any MCP client over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
1 Veeva Vault tool, no custom code.
Browse the tool name, resource and method Elaichi exposes for Veeva Vault.
- Get single Veeva Vault user by ID
ElaichiToolsToolboxes
Every team gets its own Veeva Vault toolbox.
Toolboxes scope Veeva Vault tools to Regulatory, Quality, Clinical Ops and more.
- Regulatory Affairs
- Quality Assurance
- Clinical Operations
- Medical Affairs
ElaichiToolboxesShared connections
Teammates use Veeva Vault without a credential.
See who connected each Veeva Vault account and which teams and members share it.
- Regulatory EMEA
- Quality US
- Clinical Trials
- Medical Affairs
ElaichiConnectionsAudit log
Every Veeva Vault call is on the record.
When, who, what happened, type and resource for each Veeva Vault request.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships approved.
Six steps fetch Veeva Vault users, group them, draft, get approval, post back.
Veeva Vault digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch users
Veeva Vault
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Veeva Vault
Queued
Collections and dashboards
Veeva Vault numbers, counted not generated.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Veeva Vault health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Documents
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Regulatory EMEA 34%
Quality US 27%
Clinical Trials 21%
Medical Affairs 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Veeva Vault to Claude?
First, connect Veeva Vault in Elaichi by pasting in an API key from your Veeva Vault account. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste in https://api.elaichi.ai/mcp. Sign in as yourself and Veeva Vault is available in your conversations.
Does Veeva Vault work with ChatGPT and Cursor as well as Claude?
Yes. Once Veeva Vault is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Veeva Vault once and every client you use picks it up.
What can an AI agent actually do with my Veeva Vault data?
Today the Veeva Vault connector does one thing: it looks up a single Veeva Vault user by their ID. That means an agent can tell you who is behind a user ID on an audit trail, a signature, or a document history, and whether that account is active. It cannot read documents, change records, or manage users.
Does connecting Veeva Vault give the AI everything in my vault?
No. Every call to Veeva Vault runs under the access of the person who signed in, so the agent can only look up users that person could already see in Veeva Vault. Elaichi can narrow that further with restrictions, but it can never widen access beyond what your Veeva Vault permissions already allow.
Can I stop an agent from deleting or changing things in Veeva Vault?
The Veeva Vault connector is read only: it can look up a user by ID and nothing else, so there is nothing an agent can delete or change. If you want to restrict even that lookup for some teams, Elaichi applies restrictions per action, and a blocked action is never shown to Claude, ChatGPT, or Cursor, so no prompt can reach it.
What happens to a Veeva Vault connection when someone leaves?
When you offboard someone in Elaichi, their access to Veeva Vault through Elaichi ends at once, in every client they used. If they shared a Veeva Vault connection with a team, it keeps working for everyone else. Disconnecting Veeva Vault once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Veeva Vault in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.