ZuploZuplo
LoginStart for Free
  • Documentation
  • API Reference
Getting Started
Concepts
API Management
AI Gateway
MCP Gateway
    Overview
    Getting Started
      How it works
      Connect MCP clients
      Authentication
      Cross App Access
      Configuration
        Set up the gatewayMulti-upstreamLocal developmentCapability filteringCurate toolsCurate tools (in code)McpProxyHandlerCompatibility dates
      Policies
      Observability
      ReferenceServer RegistryTroubleshooting
    MCP Server
    Developer Portal
    Development
    Deploying & Source Control
    Analytics
    Observability
    Networking & Infrastructure
    Account Management
    Programming API
    Build with AI
    Zuplo CLI
    Migration Guides
    Platform LimitsVersion Support PolicySecuritySupportTrust & ComplianceChangelog
    powered by Zuplo
    Configuration

    Compatibility dates

    The Zuplo MCP Gateway requires compatibilityDate >= 2026-03-01 in zuplo.jsonc.

    Code
    // zuplo.jsonc { "version": 1, "compatibilityDate": "2026-03-01", }

    The build fails if your project uses any MCP Gateway feature (the McpProxyHandler handler or an mcp-*-inbound policy) with a compatibility date older than 2026-03-01. Bump the date in zuplo.jsonc before adding those features.

    New Zuplo projects default to a recent compatibility date, so this only applies to existing projects being upgraded to use the MCP Gateway.

    For background on Zuplo's compatibility-date system in general, see Compatibility dates.

    Edit this page
    Last modified on May 27, 2026
    McpProxyHandlerOverview
    JSON