fold: the enterprise MCP gateway — one governed endpoint between every MCP client and every MCP server. Federation, auth, policy, rate limiting, caching, audit.
Run, debug, or bump the pinned MCP conformance suite for fold. Use when conformance fails locally or in CI, when the scheduled drift workflow flags upstream movement, or when deliberately bumping CONFORMANCECOMMIT / CONFORMANCEPKG.
Review, bump, or debug the vendored fold-console assets in gateway/console — the weekly bump PR, the console-check CI gate, and the manifest allowlist. Use when the console-sync workflow is red, when a bump PR needs review, or when deliberately moving CONSOLECOMMIT.
Triage a govulncheck failure, review a dependabot PR, or bump a dependency in fold — including the case where CI goes red with no commit behind it. Use when make vuln fails, when CI's vuln job is red, when a dependabot PR needs review, or when bumping the MCP SDK or the Go toolchain.
Work on fold-discovery and internal/kubediscovery — the controller that turns labeled Kubernetes Services into fold's discovery document, and the trust boundary its allowlist flags defend. Use when changing cmd/fold-discovery, internal/kubediscovery, gateway/discovery.go, or docs/discovery-controller.md.
Run fold locally and talk to it as a real MCP client — the dev stack, the repo's .mcp.json, and what to look at once it is up. Use to see a change from a client's side, to reproduce a client-reported bug, or when a test is green and the behavior still looks wrong.
Cut a fold release — verify gates, write the changelog and bump the Helm chart's appVersion, then with explicit per-step approval commit/push, watch CI, tag to trigger goreleaser, verify the published artifacts via the release-verifier agent, and refresh the conformance receipt. Use when the user asks to release…
Change fold's Helm chart safely — the three ci values shapes make helm-check renders against, the probe Host-header trap, Chart.yaml's two version lines, and the docs that track values. Use when editing anything under deploy/helm/, adding a value, or when make helm-check fails.
Drive the official MCP Inspector CLI against a locally running fold to see what a real client sees — namespacing, list merging, policy filtering, auth failures, ui:// resources. Use to reproduce a client-reported bug, to diff gateway behavior against an upstream directly, or to check a change by hand before writing…
Look up the normative MCP specification text for a method, field, header, or error code before implementing or changing it in fold. Use when a change touches wire behavior, when a reviewer asks "does the spec actually say that", or when answering a protocol question — never answer MCP protocol questions from memory.
Add, rename, or retire a fold metric, span attribute, or audit event field — the bidirectional lockstep against the packaged dashboard and both alert files, the v1 freeze on names and label sets, and the docs that track them. Use when touching gateway/metrics.go, otel.go, audit/, the Grafana dashboard, or either alert…
Investigate or fix fold proxy-path performance — run the added-latency gate, profile with the bench-profiler agent, and apply the move-to-snapshot-build fix pattern. Use when make bench fails, when a change touches the hot path, or when the user asks about gateway latency or allocations.
Run fold's full local merge gate in the right order and interpret failures — make check, plus the conditional gates the diff warrants (bench, conformance, helm-check, vuln, console-check, image build). Use before declaring work done, before commits, or when the user asks "is this ready" / "run the checks".
Checklist for adding state or config to fold that must survive hot reload — snapshot placement, Reload semantics, discovery merge, schema lockstep, and the reload/churn test matrix. Use when adding a config field, per-upstream setting, or any state the gateway reads per-request.
Groom fold's gap list and roadmap — README "Not implemented", docs/roadmap.md's three horizons, non-goals, deprecations on the clock, and the drift canaries that fail when a gap closes. Use when closing or widening a gap, when deciding whether something is a non-goal, or when a canary test fires.
Land a verified change in fold — branch, commit, PR title and body in the house register, the template checklist answered rather than ticked, then hand off to CI watching. Use when a change is ready to become a PR, when the user says ship it / open a PR / land this, or when work needs a branch before it grows further.
Compare a new MCP protocol revision against what fold implements and produce the gap list — what fold must change, what it may decline, and what becomes a deliberate documented gap. Use when a new revision ships, when the conformance drift workflow flags upstream movement, or when bumping the Go SDK across a protocol…
Work on fold-stdio and internal/stdiobridge — the shim that exposes a stdio MCP server over streamable HTTP so the gateway can federate servers with no network endpoint. Use when changing cmd/fold-stdio, internal/stdiobridge, the stdio compose profile, or docs/stdio.md.
Bring fold's docs in line with the working diff — map changed code to the README sections, docs/ guides, schema, and example config that track it, then fix the drift via the docs-sync agent. Use when the user asks to update docs, when the Stop hook flags code changes without doc changes, or before committing a…
Watch fold's CI after a push or tag and triage failures back to local make targets. Use immediately after any git push, when the user asks about CI status, or when a run needs diagnosing.