ZuploZuplo
LoginSign Up
  • Documentation
  • API Reference
Introduction
Getting Started
    Develop using the Portal
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth4 - Deploy5 - Dynamic Rate LimitingMCP - Quick start
    Develop Locally
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth
Concepts
Development
Policies
Handlers
API Keys
MCP Server
MCP Gateway
    IntroductionBetaQuickstartQuickstart (Local Dev)How it works
    Connect MCP clients
    Authentication
    Configuration
      Set up the gatewayMulti-upstreamLocal developmentCapability filteringCurate toolsCurate tools (in code)McpProxyHandlerCompatibility dates
    Observability
    ReferenceTroubleshooting
AI Gateway
Developer Portal
Monetization
Deploying & Source Control
Observability
Networking & Infrastructure
Account Management
Programming API
Build with AI
Zuplo CLI
Migration Guides
Platform LimitsSecuritySupportTrust & ComplianceChangelog
powered by Zudoku
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
McpProxyHandlerAnalytics
JSON