Skip to main content
Use Nango through Corsair: one client, typed API calls. The Nango API authenticates with an environment secret key (Environment settings > API keys). Use the key of the environment you want the agent to work in (dev or prod); a scoped key limits which operations succeed. The plugin covers integrations, connections, Connect sessions, functions, syncs and records, tool calls, legacy actions, providers, environment variables and the proxy (GET, POST, PUT, PATCH, DELETE). Secrets. connections.get drops the connection’s third-party credentials unless you pass include_credentials: true, and connections.import never returns the credentials it sent. integrations.get with include: ["credentials"] and environment.getVariables return secrets in plain text. Errors never carry the request body or the environment key. Risk. Proxy writes, tool calls and legacy actions act on your end customer’s third-party account, so they are destructive, as are deletes, connections.setMetadata (replaces all metadata) and connections.import (can overwrite a connection’s credentials). Not included: environment and API-key administration, webhook signing-key rotation, function compile/deploy, sync variants, record pruning and inbound webhooks. What you get:
  • 35 typed API operations

Setup

1

Install

2

Add the plugin

corsair.ts
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

4

Connect a tenant

Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.

Example API calls

connections.list
sessions.create
See the full list on the API page.

What’s next

API reference

Every nango.api.* operation with input and output types.

Connect / OAuth

createLink, Hub delivery, and tenant connect flows.

Use with agents

Expose this plugin’s operations as MCP tools.