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
Nango connection identity, OAuth/provider configuration, secret management, environment separation, and end-user authorization apply.
05 · Monitoring, approval, and recovery
Keep customer credentials isolated, scope every action, handle token refresh, retries and rate limits, and log upstream execution.
06 · Gaps and implementation limits
Nango is integration infrastructure; it does not make an upstream API safe or semantically consistent by itself.
Agent access
MCP and adjacent posture
MCP integration infrastructure; upstream capabilities varyNango integration infrastructure and MCP client/toolingCurrent documented service
Role: infrastructure
Read scope: Depends on connected upstream APIs and MCP servers.
Write scope: Depends on connected upstream APIs and MCP servers.
Authentication: Managed OAuth and customer-facing connection infrastructure
Approval boundary: Consequential writes should require explicit review; use vendor confirmation controls where available.
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 interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Nango ships these experiences.
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 ↗Nango connects products to third-party MCP servers and supplies white-label auth, sync, webhook, and integration infrastructure; it is not one business SaaS provider.
- Publisher updated
- Jul 10, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party infrastructure review
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.
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.
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.
Webhooks / extensionsSource inventory
https://docs.nango.dev/guides/webhooks ↗First-party event, extension, or embedding documentation.
- 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 the representative first-party source or targeted access review.
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.