fold: the enterprise MCP gateway — one governed endpoint between every MCP client and every MCP server. Federation, auth, policy, rate limiting, caching, audit.
Diagnoses fold proxy-path latency and allocation regressions — runs the added-latency gate, profiles the hot path, and pinpoints which change put work on the per-request path. Use when make bench fails, before merging proxy-path changes, or when the user asks about gateway performance.
Reviews fold's deployment surface — the Helm chart's rendered output, Kubernetes security posture, the four Dockerfiles, and the compose stack — for what only shows up in the manifest rather than in the templates. Use after changes under deploy/, before a chart release, or when auditing how fold actually runs in a…
Audits fold's documentation surface after a feature or behavior change — README sections, docs/ guides, config schema lockstep, and the "Not implemented" gap list. Use after implementation is done, before commit.
Diagnoses an intermittent or race-detector test failure in fold — reproduces it reliably, localizes the shared state or timing assumption behind it, and names the real fix. Use when a test fails in CI and passes locally, when go test -race reports a data race, or when a test is suspected of being timing-dependent.
Reviews fold changes against the gateway's architectural invariants — pipeline order, snapshot-based reload state, audit as the single exit door, the invisibility rule, the minted error-code registry, and proxy-path allocation discipline. Use proactively after any non-trivial change to gateway/, auth/, policy/, or…
Writes and extends fold's integration tests using real MCP SDK peers behind the gateway. Use when a change needs test coverage — new gateway behavior, reload/discovery paths, policy or auth changes, or a repro for a reported bug.
Audits fold against the normative MCP specification for the pinned revision — method shapes, required fields and headers, error-code allocation, caching and intermediary rules, and deprecations on the clock. Use when a change touches wire behavior, when a new protocol revision ships, or before bumping the conformance…
Verifies a published fold release end to end from the outside — archives, checksums and their cosign signature, SBOMs, the four ghcr images, the OCI chart, and every sigstore attestation. Use after a tag's release workflow goes green, before announcing a release, or when someone asks whether a published artifact is…
Security review of fold changes against the documented threat model — inbound auth chain, deny-by-default policy, credential confinement, tenant isolation, and the trust boundaries in docs/security-model.md. Use for changes to auth/, policy/, host validation, EMA, discovery, or credential handling, and for periodic…