01 · Records and state owned
Integrations, providers, OAuth credentials, connections, syncs, actions, webhooks, proxy requests, and upstream MCP/server configurations.
Nango
Nango
A major integration infrastructure platform covering hundreds of APIs, with authorization, proxying, syncs, webhooks, rate-limit handling, logs, and agent-tool patterns that reduce the hidden work under multi-system BYO-UI.
Interface hosts, builders & integration infrastructureInterface host and orchestration layerExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Broker authorized access to upstream APIs and MCP servers and retrieve connection, sync, or integration context.
03 · Actions and write paths
Execute configured upstream actions and sync workflows according to each integration’s implementation.
04 · Authentication and permissions
MCP Generic discovers OAuth metadata and scopes, requires PKCE, and identifies Nango through CIMD, DCR, or a placeholder client ID without storing a client secret.
05 · Monitoring, approval, and recovery
Keep customer credentials isolated, scope every action, handle token refresh, retries and rate limits, and log upstream execution.
06 · Limits and caveats
MCP Generic is an authorization integration, not a normalized tool contract; available objects, reads, writes, and business safeguards come from each connected MCP server.
Agent access
MCP support
Integration infrastructureNango integration infrastructure and MCP client/toolingCurrent documented service
Support: Integration infrastructure
Read scope: Depends on connected upstream APIs and MCP servers.
Write scope: Depends on connected upstream APIs and MCP servers.
Authentication: OAuth 2.0 discovery with PKCE; Nango selects CIMD, then DCR, then a static placeholder flow, with automatic scope discovery and no client-secret storage for MCP Generic.
Approval boundary: Nango completes upstream OAuth authorization; the BYO-UI must separately confirm consequential tool invocations, display the connected server and granted scopes, and enforce domain-level action policy.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access2
UI extensibility4
Portability3
Observability4
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Nango ships them.
Single-platform patterns
- Managed integration layer beneath a multi-system BYO-UI
- BYO-UI application shell
- Capability gateway
- Agent and tool operations console
Multi-platform compositions
- Nango + systems of record: byo-ui application shell
- Nango + systems of production + systems of engagement: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCP / agent-role validationRepresentative source
https://nango.dev/docs/integrations/all/mcp-generic ↗MCP Generic OAuth and scope discovery, PKCE, client-identification fallbacks, compatibility requirements, and self-hosted CIMD deployment boundary
- Publisher updated
- Jul 12, 2026
- BYO-UI reviewed
- Jul 22, 2026
MCP Generic authorization and self-hosting requirements reviewed 2026-07-22
Developer docsSource inventory
https://nango.dev/docs/guides/platform/webhooks-from-nango ↗Current first-party guide documents signed webhooks from Nango, event types, retries, external webhook forwarding, and environment-specific URLs.
- Publisher updated
- Jul 10, 2026
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
DocumentationSource inventory
https://docs.nango.dev/ ↗First-party integration documentation.
- Publisher updated
- May 19, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://nango.dev/ ↗Platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Integration catalogSource inventory
https://nango.dev/integrations ↗First-party provider catalog.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.