The MCP server now runs from its own apivault-mcp repository and holds no database credentials. It talks to new /api/mcp/v1/keys endpoints on ApiVault, which enforce keys:read, keys:write, and keys:reveal on each route.

Custom vault keys and decryption stay on the ApiVault backend, not in the MCP server.

The server hosts its own RFC 9728 protected resource metadata, pointing to ApiVault as the OAuth 2.1 authorization server. To host it elsewhere, set MCP_RESOURCE_URL.

Learn more in the MCP documentation.