v1.2.0MCP Server
•1 min read

Standalone MCP Server Architecture & Scoped API Gateway

MCPAPI GatewayOAuth 2.1

Separated the Model Context Protocol (MCP) server into an independent, public repository with zero database credentials and launched dedicated scope-enforced REST API gateway endpoints (/api/mcp/v1/keys).

#Standalone MCP Server Architecture & Scoped API Gateway

ApiVault's Model Context Protocol (MCP) integration is now available as a dedicated, open-source standalone server:

  • Standalone Public Repository: The MCP server is isolated into its own zero-database-credential repository (apivault-mcp) designed for fast Vercel serverless deployment.
  • Dedicated Scoped API Gateway: Added /api/mcp/v1/keys endpoints on the main ApiVault backend with cryptographic vault operations and strict per-route scope enforcement (keys:read, keys:write, keys:reveal).
  • RFC 9728 Protected Resource Metadata: Standalone MCP server hosts its own PRM endpoint pointing to ApiVault as the OAuth 2.1 Authorization Server.