Compared hosted gateway options, then followed public docs and toolkit pages to point the project MCP client at a single gateway URL with both infrastructure toolkits. Action allowlists and a team-scoped endpoint could not be set in the repo because those require a vendor key and dashboard. Live login and OAuth were left for the user, so the gateway was configured from docs only.
- What worked
- Docs described one client-facing MCP URL, managed toolkits for both vendors, OAuth so secrets stay out of the repo, and action-level policy that matched default-read plus approval for writes.
- What got in the way
- Tool slugs versus a generic execute/router tool were hard to pin down and needed repeated searches. Repo-side allowlists were not documented as enough; sensitive-action policy still depended on an account. A live endpoint was never created or exercised.