**Source URL:** https://limited.veevavault.dev/safety/vault-dx/plugins/overview

# Overview

Veeva Claude Plugins for Vault are installable skill packages that teach Claude Code to work with Veeva Vault. Each plugin ships a set of skills, structured instructions that tell Claude when and how to assist with a specific Vault task.

## Available plugins

Veeva Claude Plugins are available from the `veeva-claude-plugins` marketplace:

| Plugin | For | What it does |
| --- | --- | --- |
| [`vault`](/safety/vault-dx/dx-reference/plugin-reference/vault/) | All Vault users | Sign in to a Vault, query data with VQL, and profile application family and environment |
| [`vault-administrator`](/safety/vault-dx/dx-reference/plugin-reference/vault-administrator/) | Vault administrators | Author MDL configuration, manage file staging, author reports and dashboards, and pulling Vault configurations |
| [`vault-developer`](/safety/vault-dx/dx-reference/plugin-reference/vault-developer/) | Vault developers | Generate Vault Java SDK entry-point classes, scaffold Custom Pages, call the Vault API, Vault AI agents |

Plugins work together. `vault-administrator` depends on `vault` for sign-in and data access. `vault-developer` depends on both. Install only the plugins you need. Claude Code installs declared dependencies automatically.

## Plugin Components

Each plugin is made up of one or more of the following components:

**Skill:** Teaches Claude a specific task. Skills trigger when Claude matches the user's intent to the skill's trigger phrases, or when the user invokes the skill explicitly with `/plugin-name:skill-name`.

**MCP Server:** Claude Plugins connect Claude to the remote Vault Documentation MCP at `docs.veevavault.dev/mcp`, which answers questions from official Vault reference docs rather than guessing at endpoints or syntax.

## Vault CLI

Claude Plugins use [Vault CLI](/safety/vault-dx/cli/) wherever applicable. For operations the CLI does not cover, plugins call the Vault API directly. The CLI is recommended but not required. Plugins fall back to the Vault API when the CLI is absent and can install it for you when prompted.

## Application Families & Environments

When connected to a Vault, Claude Plugins identify:

*   **Application Family:** Clinical, Commercial, Medical, Quality, Regulatory, Safety, or Platform. The application family determines which standard objects, APIs, and features are present. Claude customizes its answers to what your specific Vault supports.
*   **Environment type:** `PRODUCTION`, `SANDBOX`, `DEMO`, `TEST`, or `UNKNOWN`. Writes require your explicit confirmation on non-production Vaults. Against a production or unknown Vault, Claude hands you the exact command rather than running it.
*   **API version:** Vault releases a new API version every four months. Claude notes version-gated features and does not suggest unavailable functionality.

---

**Previous:** [Claude Plugins](/safety/vault-dx/plugins)  
**Next:** [Getting Started](/safety/vault-dx/plugins/getting-started)