The MCP server now operates from its own apivault-mcp repository and holds no database credentials. It communicates exclusively with dedicated /api/mcp/v1/keys endpoints on ApiVault, enforcing keys:read, keys:write, and keys:reveal per route.

Encryption and decryption run on the ApiVault backend. The MCP proxy forwards custom vault keys with requests that need them and does not persist them.

The server hosts RFC 9728 protected resource metadata, designating ApiVault as the OAuth 2.1 authorization server. Self-hosted deployments can specify custom endpoints via MCP_RESOURCE_URL.

Learn more in the MCP documentation.