Vault Documentation MCP + Vault MCP Server

Endpoint

Hosted endpoint · transport

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

Tool quality observed · not scored

From an anonymous initialize + tools/list capture measured 2026-10-20; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.

Tools

• search_documentation — Search Vault developer and help documentation. Each result includes a `content_url` (rendered HTML) and a `markdown_url` (Markdown). Fetch `markdown_url` when results are incomplete or the task needs full context. SDK and VAPIL javadocs have no `markdown_url`. ## Sources - `vault_developer_documentation`: Vault Developer Portal (Java SDK, API, MDL, VQL, Direct Data API, Custom Pages, Vault AI) and Vault CRM Developer Portal. Use vault_crm+limited for CRM. - `vault_api_reference`: API endpoint reference — URIs, parameters, response attributes, error types. Use vault_crm+limited for CRM. - `vault_java_sdk_javadocs`: Vault Java SDK javadocs — classes, methods, parameters, return types, exceptions. - `vapil_javadocs`: VAPIL javadocs — classes, methods, code examples. - `vault_help_documentation`: End-user and admin docs. Vault Help and Vault CRM Help. Use vault_crm+limited for CRM. ## Releases Defaults to general. `vapil_javadocs` is general-only. Help, developer, and API sources with vault_crm are limited-only. - `general`: ~every four months; includes all limited enhancements since prior general release. - `limited`: ~every 3–5 weeks; early access to new features. ## App Families Defaults to platform. Ask user if unclear for developer, API, and help sources. `vapil_javadocs` and `vault_java_sdk_javadocs` are platform-only. Always use release=limited with vault_crm. - `platform`: Base Vault platform. - `commercial`: PromoMats, Portal - `qualityone`: Document Control, QMS, HACCP, HSE, Training - `quality`: QualityDocs, Training, Station Manager, QMS, Surveillance, Validation Mgmt, Batch Release, HACCP - `medical`: MedComms, Medical Inquiry, Portal - `clinical`: CTMS, eTMF, Payments, SSU, Disclosures, Site Connect, OpenData Clinical - `regulatory`: Submissions, Submissions Archive, Submissions Publishing, Registrations - `safety`: Safety, Safety Workbench, Safety Signal, SafetyDocs
• search_release_notes — Search Veeva Vault release notes to find features, changes, and enhancements introduced in a specific release or range of releases. Each result includes a `content_url` (rendered HTML) and a `markdown_url` (Markdown). Fetch `markdown_url` when the query asks for a complete feature list (e.g. "what's new in 26R2?") — search results cover only a subset. Also fetch when results share the same `markdown_url` or content is incomplete. ## Sources - `vault_developer_release_notes`: Vault Developer Portal — Java SDK, API, VQL, MDL, Direct Data API, platform developer features. - `vault_help_release_notes`: Vault Help site — platform and app-family features for end users and admins. - `vault_crm_release_notes`: Vault CRM Help site. - `vault_crm_developer_release_notes`: Vault CRM Developer Portal — X-Pages, X-Pages Studio, CRM REST API. ## Release Format Major version only (e.g. `26R2`, `25R1`). - `start_release`: Optional. Omit to search all releases. - `end_release`: Optional upper bound (requires `start_release`). E.g. `start_release=24R1`, `end_release=26R2` searches that span. ### Point Release Mapping Point releases (minor > 0, e.g. 26R2.1) deliver features for the *next* major release. Apply the same mapping to both `start_release` and `end_release`: | User asks about | Use release | | ---------------- |-------------| | 26R2.0 (GA) | `26R2` | | 26R2.1 – 26R2.x | `26R3` | | 26R1.1 – 26R1.x | `26R2` | | 26R3.1 – 26R3.x | `27R1` | GA (`.0`) uses its own release; any point release (`.1`+) uses the next release. This applies to both `start_release` and `end_release`.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/vault-documentation-mcp-vault-mcp-server"

curl "https://apis.io/api/v1/mcp?limit=25"