Skip to content

ViperJuice/mcp-gateway

v1.10.0 Breaking

This release includes 2 breaking changes for platform teams planning a safe upgrade.

Published 1mo MCP Servers
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Affected surfaces

breaking_upgrade auth

Summary

AI summary

New runtime lifecycle APIs and safer default refresh/disconnect behaviors with migration guidance for eager startup.

Full changelog

Added

  • gateway.connect_server, gateway.disconnect_server, and
    gateway.restart_server provide runtime-only lifecycle controls for known
    downstream servers with structured status output.
  • gateway.health now includes optional startup policy fields for eager, lazy,
    skipped, policy-denied, missing-auth, and unknown autoStart decisions.
  • pmcp status --verbose displays live startup policy details when available,
    including missing-auth environment variable names without exposing secret
    values.
  • Startup and refresh logs now include concise policy summary counts and
    actionable messages for unknown autoStart and missing-auth skips.
  • pmcp doctor now includes a named http check that probes gateway /health
    reachability without requiring bearer auth.
  • Bounded multi-client soak coverage now exercises concurrent lazy invokes,
    same-server single-flight startup, refresh and lifecycle refusal/cancellation,
    health/list-pending/status visibility, and local HTTP shared-service smoke
    paths.

Changed

  • gateway.refresh now refuses by default while downstream requests are pending
    and reports pending-request counters. Passing force=true cancels those
    requests before refresh proceeds.
  • gateway.disconnect_server and gateway.restart_server use the same
    target-server pending-request policy: refuse by default and cancel only that
    server's pending requests when force=true.
  • Packaged manifest entries no longer mark Playwright or Context7 for automatic
    eager startup. Downstream servers remain lazy by default and can be eagerly
    started by adding their names to top-level .mcp.json autoStart.
  • README and pmcp setup guidance now describe the user-owned startup model:
    mcpServers provides lazy availability, while autoStart opts selected
    servers into eager startup.
  • README and SECURITY now document shared-service HTTP mode, per-source-IP
    /mcp rate-limit buckets, lifecycle disruption behavior, and unauthenticated
    /health and /metrics expectations.

Migration

  • To restore the previous eager startup behavior for the common browser/docs
    stack, add:
    {
      "autoStart": ["playwright", "context7"],
      "mcpServers": {}
    }
    

Breaking Changes

  • `gateway.refresh` now refuses by default when downstream requests are pending; `force=true` required to cancel them.
  • `gateway.disconnect_server` and `gateway.restart_server` refuse by default with pending‑request counters; `force=true` cancels only that server's pending requests.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track ViperJuice/mcp-gateway

Get notified when new releases ship.

Sign up free

About ViperJuice/mcp-gateway

A meta-server for minimal Claude Code tool bloat with progressive disclosure and dynamic server provisioning. Exposes 9 stable meta-tools, auto-starts Playwright and Context7, and can dynamically provision 25+ MCP servers on-demand from a curated manifest.

All releases →

Beta — feedback welcome: [email protected]