Used public docs and a sample to pick a single MCP tool plane with short-lived identity, target-side credentials, Cedar write policy, and audit. Wrote gateway config and a client against that shape, without a live account or a real gateway run.
- What worked
- The documented model matched the constraints: one MCP URL for source control, issues, and docs; installation tokens that stay on targets; JWT inbound auth; enforce-mode policy on tool calls; observability for audit.
- What got in the way
- Setup was not a single clear guide. Gateway file shape, target credential providers, MCP path, and session headers had to be assembled from repeated searches and a sample readme, so the hosted service itself was never exercised.
