Veeva MCP Server

Veeva CLM Generator & Workflow for building iRep Presentations.

Local serverstdio

What is the Veeva MCP server?

Veeva CLM Generator & Workflow for building iRep Presentations. The veeva mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

If you're developing and managing multiple Veeva CLM projects, it can be time-consuming to manage consistent code and workflows. This package centralizes core functionality for building and deploying Veeva CLM Presentations.

Its toolset

Everything the assistant can do here goes through one of these:

  • Prerequisites — No other system-level dependencies are required. Image processing is handled internally by sharp
  • Installation — The Installation tool exposed by this server
  • Sass — The Sass tool exposed by this server
  • JavaScript — The JavaScript tool exposed by this server
  • Usage — The Usage tool exposed by this server
  • Options — The Options tool exposed by this server

Configuration

  • Node.js v22 or later No other system-level dependencies are required. Image processing is handled internally by sharp.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at veeva on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Veeva's toolset — Prerequisites, Installation, Sass and 3 more — is a fair guide to whether it matches your workflow. It is maintained by sbritton; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the veeva mcp server does with a few real requests.

Available tools

ToolWhat it does
PrerequisitesNo other system-level dependencies are required. Image processing is handled internally by [sharp](https://sharp.pixelplumbing.com/).
InstallationThe Installation tool exposed by this server.
SassThe Sass tool exposed by this server.
JavaScriptThe JavaScript tool exposed by this server.
UsageThe Usage tool exposed by this server.
OptionsThe Options tool exposed by this server.

How to install the Veeva MCP server

{
  "mcpServers": {
    "veeva": {
      "command": "npx",
      "args": ["-y", "veeva"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js v22 or later No other system-level dependencies are required. Image processing is handled internally by sharp.

Example prompts to try

  • Use Veeva to Prerequisites.
  • Use Veeva to Installation.
  • Use Veeva to Sass.

Frequently asked questions

It connects Veeva to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Prerequisites, Installation, Sass, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Veeva directly.