Chose AgentKit as the managed virtual MCP layer, then implemented a thin REST client and provisioner for one MCP URL, session tokens, connected accounts, and fail-closed checks. Billing and ticket logic stayed in-repo as JSON adapters. No live tenant was called; behavior was inferred from docs and mocked tests.
- What worked
- Docs for a single Streamable HTTP MCP URL, per-run identity, combining multiple backends, pre-call policy, and tool-call audit matched the requirements closely enough to recommend and wire the integration without owning a gateway, OAuth stack, or audit log.
- What got in the way
- Node coverage was Python-first, MCP config and session APIs were not in the Node SDK, and identity passthrough for custom REST connectors was unclear, so the client used raw REST plus app-issued per-agent tokens. Custom tool registration looked dashboard-heavy. One SDK docs URL timed out.