Nango for AI agents

Nango is a unified API platform that lets developers connect to hundreds of third-party services through pre-built, customizable integrations instead of building each one from scratch. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Developer toolsAPI keyMCP + RESTnango.dev
AUDIT LOG · NANGOPOLICY: acme-support
09:41:07 · claude · u_8f2read
nango.list_connections
List Connections✓ allowed · 212ms
09:41:08 · claude · u_8f2read
nango.get_proxy
Proxy GET Request✓ allowed · 164ms
09:41:09 · claude · u_8f2write
nango.create_integration
Create Integration✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
nango.delete_connection
Delete Connection✕ blocked · policy: deny
EVERY NANGO CALL, ON THE RECORD
01 · USE CASES

What agents do in Nango.

01

Check a connection's sync status

Look up whether a synced integration is up to date before troubleshooting a data gap, read-only.

02

Trigger a data sync

Trigger a sync for a connection to pull the latest data from a linked service.

03

Approve before deleting a connection

Require approval before deleting a connection, since it disconnects that integration entirely.

02 · ACTIONS

24 Nango actions, graded by risk.

Every Nango action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • nango.get_proxy
    Proxy GET Request
  • nango.get_connection
    Get Connection with Credentials
  • nango.get_integration
    Get Integration
  • nango.get_sync_status
    Get Sync Status
  • nango.list_connections
    List Connections
  • nango.list_integrations
    List Integrations
  • nango.get_environment_variables
    Get Environment Variables

write

15

Create and change things. Allow, or ask the user first.

  • nango.add_connection
    Add Connection
  • nango.create_integration
    Create Integration
  • nango.update_integration
    Update Integration
  • nango.create_connect_session
    Create Connect Session
  • nango.update_connection_metadata
    Update Connection Metadata
  • nango.put_proxy
    Proxy PUT Request
  • nango.connection_get
    List Connections
  • nango.edit_connection
    Edit Connection
  • nango.providers_get_get
    Get Provider Details
  • nango.sync_trigger_post
    Trigger Sync
  • nango.providers_list_get
    List Providers
  • nango.scripts_config_get
    Get Integration Functions Configuration
  • nango.action_trigger_post
    Trigger Nango Action
  • nango.reconnect_session_post
    Reconnect Session
  • nango.set_connection_metadata
    Set Connection Metadata

destructive

2

Delete, cancel or archive. Ask first, or deny outright.

  • nango.delete_connection
    Delete Connection
  • nango.delete_integration
    Delete Integration
03 · HOW IT WORKS

Nango in three steps.

  1. 01Your users connect NangoThey add their Nango api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Integration” can wait for the user, and “delete Connection” can be denied outright.
  3. 03Any agent can actYour agent calls Nango through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('nango', {
  read: 'allow',
  write: 'ask',        // create_integration
  destructive: 'deny',  // delete_connection
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Nango connects.

Users add their Nango api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Nango connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Nango from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Nango and Arc0, answered.

Q01

Can I use Nango with Claude, ChatGPT or Cursor?

Yes. Connect Nango to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Nango actions you allow.

Q02

How do users connect Nango?

Users add their Nango api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Nango actions can my agent take?

24 in total: 7 read, 15 write and 2 destructive, such as “create Integration”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Nango?

Yes. Actions like “delete Connection” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Nango too?

Yes. The same Nango connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Nango into your agent.

Your users connect Nango once, under your brand. Your agent gets 24 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan