Nango
Also known as: Nango.dev, Nango Agent Sessions
Nango lets software developers connect their agents to external APIs and MCP tools. It stores and refreshes credentials, sets which connections an agent can use and runs tools such as creating a Linear issue or updating a customer record. Its triggers can wake an agent when data changes, and its sync functions can deliver records to an application's own storage. Teams can inspect traces and test new integration functions before deployment.
Nango provides the integrations that an application or AI agent uses to work with external services. The platform manages authentication for API connections, runs tools and syncs data from the systems a user has authorized. Nango's MCP platform offers more than 10,000 tools across more than 1,400 APIs. A developer can expose a narrower set to a particular agent so a user can create a calendar event, update a record or open a Linear issue without giving the model the credential for the underlying service.
A developer creates an Agent Session for a user or organization and selects the connections, integrations and tools that can be used in that session. When the agent calls a tool, Nango makes the request with the appropriate credentials. The developer can connect through an MCP interface or use server tools in the application.
Developers can also write TypeScript functions when a workflow needs custom inputs, outputs or an API action beyond the supplied catalog, and can contribute integrations to Nango's open source repository. A proxy can pass calls to a supported endpoint with the authorization associated with the connection. Embeddable authorization screens can carry the customer's own branding.
Nango can receive provider webhooks and normalize them into events for a customer application. When an API lacks the relevant webhook, Nango can poll for changes instead. Its syncs can save a checkpoint and fetch records changed since the prior batch. The customer application can receive a notification, pull the records and store them in its own database or retrieval system. The same integration layer can serve both a background sync and a tool that the agent calls during a conversation. The application determines how to use the changed data.
The platform holds a SOC 2 Type 2 report, signs HIPAA business associate agreements and supports role based access, SAML or OIDC single sign on, SCIM and an account audit trail. Teams can use isolated environments for integration testing, inspect traces for successful or failed runs and export them in OpenTelemetry format. Nango Cloud runs in the US, and Enterprise customers can self host or run a bring your own cloud instance in any AWS, Google Cloud or Azure region. The free plan has hard monthly caps on connections, compute and data transfer. Pay as you go costs $50 per month and includes $50 in usage credits, with each connection billed at $0.29 a month, compute at $0.72 an hour and egress at $0.50 per GB.
Replit used Nango to power connector triggers for more than 30 integrations, and Motion launched 189 integrations using the platform. Nango fits product and engineering teams that need to maintain authentication, tool actions and data access across a range of external services. A developer can set a different scope for each user's agent session, while the application remains responsible for its model, conversation and business decisions. When a connected service returns an error, the team can inspect the associated tool or sync request and change its integration independently of the agent's instructions.
Vendor details
Canonical URL
https://nango.dev/
Category
Agent infrastructure
Subcategory
Agent tool calls, delegated API credentials and synchronized context
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Agent Sessions over MCP or API, OAuth, TypeScript functions and connectors for services such as Linear, Slack, Gmail and Salesforce.
In practice
A product assigns a scoped Agent Session that permits issue creation for the authorized Linear user.
A support platform receives a standardized webhook when a connected account has a relevant update.
An engineering team tests a custom TypeScript tool against a development connection and reviews the trace before release.
Sources & related URLs
Related / legacy domains
Research sources
Agentic Index coverage score
10.5 / 14 capabilities · 75%
| Integrations & Tool Calling | Full |
|---|---|
|
Nango runs API tools using credentials held for an authorized connection. An agent can create a Linear issue, update a CRM record or post to Slack through the offered tools. A developer can expose a specific set of connections and tools per Agent Session. The integration layer handles the underlying authentication and can use the request proxy for additional endpoints. Sourcenango.dev/platform/mcpread 2026-11-20 |
|
| Workflow Orchestration | Partial |
|
An event can start a custom integration function, a sync can supply records and a tool can update a connected service. A TypeScript function can carry several operations for a purpose chosen by the developer. Nango runs those integrations and the application decides what happens next. The service does not coordinate separate agents in a graph of model decisions and business steps. Sourcenango.dev/platform/triggersread 2026-11-20 |
|
| Knowledge Grounding & RAG | Full |
|
Context Sync delivers records from external tools to an application so the agent can use a current copy. A developer can route changed records into a database, object store or vector store. The integration can track what changed and notify the application after a sync. The application can also fetch additional context through a connection when a particular tool needs it. Sourcenango.dev/platform/context-syncread 2026-11-20 |
|
| Human Oversight & Guardrails | Partial |
|
A user authorizes the external service, and the application chooses which connected tools the agent can call in its session. The developer can keep an operation out of the scope unless the application has already collected permission. These controls govern delegated access. The application has to provide its own live reviewer queue for particular actions such as approving a record write. Sourcenango.dev/docs/guides/agent-sessionsread 2026-11-20 |
|
| Security, Identity & Governance | Full |
|
Credentials are encrypted in Nango and associated with the connection for a specific user or organization. A session can restrict which connections and tools the agent may use, and the model can call an approved tool without receiving the credential. Teams control member permissions with role based access control, sign in through SAML or OIDC single sign on, provision users with SCIM and review an audit trail of account changes. The platform holds a SOC 2 Type 2 report and signs HIPAA business associate agreements. Sourcenango.dev/platform/mcpread 2026-11-20 |
|
| Observability & Auditability | Full |
|
The platform captures traces for tool calls, syncs and webhook processing and records integration failures. A developer can inspect the execution and the log messages produced by a custom function. Available plans can export traces in OpenTelemetry format. Users can also check where a sync stopped and inspect related events before restarting or correcting a run. Sourcenango.dev/pricingread 2026-11-20 |
|
| Memory & State Persistence | Partial |
|
A sync can save a checkpoint after each batch and resume at that point after an interruption. The connection can also retain a customer's field mapping, configuration and scoped credentials. Future syncs can use the same connection settings. The application still owns its conversation history and any memory the agent needs when it returns to a user's task. Sourcenango.dev/platform/data-syncread 2026-11-20 |
|
| Deployment & Data Residency | Full |
|
Nango Cloud keeps encrypted sync records temporarily on AWS in the US, pruning them 30 days after their last update and clearing them if a sync stops for 60 days. Enterprise customers can run Nango on their own infrastructure or as a bring your own cloud instance in any AWS, Google Cloud or Azure region. The application can pull changed records and store them in the system it operates. Sourcenango.dev/platform/data-syncread 2026-11-20 |
|
| Prebuilt Agents / Templates / Packs | Full |
|
The MCP catalog provides more than 10,000 tools across more than 1,400 APIs, including actions such as opening a Linear issue and updating a CRM contact. Developers can use ready tools, triggers and syncs and can replace supplied logic with custom functions. The organization can restrict how those pieces are exposed to the user and agent through the Agent Session. Sourcenango.dev/platform/mcpread 2026-11-20 |
|
| Triggers & Channel Coverage | Full |
|
Nango receives provider webhooks and can poll APIs that do not supply the right change event. A customer application gets a standardized event and can start the agent with the changed record. The developer can choose how often the integration polls. When the source supports a native webhook, the application can act as the record changes instead of waiting for a poll. Sourcenango.dev/platform/triggersread 2026-11-20 |
|
| Model Flexibility & Routing | Not documented |
|
Nango provides the actions and context needed by an agent built elsewhere. When the application chooses an agent framework or model, it can attach the MCP catalog through a supported client. Model choice remains with the application. The integration runtime has no model selector or model routing engine for picking a provider according to a prompt, latency or cost. Sourcenango.dev/docs/guides/agent-sessionsread 2026-11-20 |
|
| APIs / SDKs / MCP Extensibility | Full |
|
Developers can use Agent Sessions through MCP or the API and can write integration functions in TypeScript. Actions can call endpoints the catalog does not cover through the request proxy. The platform can also expose management capabilities for starting or stopping a sync at a particular connection. Developers can maintain integration code in their own repository and deploy it to the runtime. Sourcenango.dev/blog/how-to-build-a-gmail-api-integration-with-nango-and-clauderead 2026-11-20 |
|
| Testing, Debugging & Optimization | Full |
|
A developer can run a TypeScript integration against a test connection before deploying it. The dry run can issue the real API call with the credentials for that environment so a developer can see input and provider errors. Separate environments help stage changes, and execution traces help locate a specific failed request. The test workflow checks whether the integration performs its intended action. Sourcenango.dev/blog/how-to-build-a-gmail-api-integration-with-nango-and-clauderead 2026-11-20 |
|
| Browser / Computer-use | Not documented |
|
The integration service gives an agent authorized tools for reading and changing records through APIs. Those tools can take actions in external applications such as opening a ticket or adding a calendar event. The execution stays within the integration runtime. There is no browser session in which the agent clicks an application's controls or drives a remote desktop outside those API tools. Sourcenango.dev/platform/mcpread 2026-11-20 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
$50 per month with $50 in usage credits
Base fee, connections, compute time and egress
Included quota
Free is hard capped each month at 10 connections, 10 compute hours and 10 GB of data transfer. Pay as you go includes $50 in usage credits each month.
What is public
Free includes 10 connections, 10 compute hours per month and 10 GB of monthly transfer. Pay as you go costs $50 per month and includes $50 in credits.
Billing mechanics
Pay as you go meters $0.29 per connection monthly, $0.72 per compute hour and $0.50 per GB of egress. Connections are prorated.
Overage / add-ons
Pay as you go meters $0.29 per connection a month, prorated, $0.72 per compute hour with each run rounded up to the second, and $0.50 per GB of egress; ingress is free.
Sales call required
No, self serve available
Free / trial
Free with metered caps
Lowest paid plan
Pay as you go
Commercial notes
A Growth add on costs $450 a month and shortens delivery of requested integrations to five days, with a shared Slack channel. Enterprise agreements bring commitment discounts, with connections as low as $0.01 a month at scale, plus self hosting, a bring your own cloud option, an MSA and SLAs. Startups can receive up to $10,000 in credits and the Growth add on free for six months.
Missing data
The Enterprise agreement determines commitment discounts and deployment charges.
Related vendors
- AgentOps — Agent observability and debugging platform: open source SDKs trace…
- AgentPhone — AgentPhone gives the AI agents a team builds their own US or…
- Agno — Python agent framework and AgentOS runtime (formerly Phidata) for…
- Airbyte — Airbyte moves data from operational systems into warehouses and…
- AIsa — Resource and payment gateway for AI agents, with one key to 110+…
- Albato — Albato is a no code integration platform that sells an embedded,…
Alternatives to Nango
Other products that do the work Nango does, and what each one is.