Skip to content

IPAAS

Nango MCP connector

The Nango connector brings Nango's connections, connect sessions, and provider setups into Claude, ChatGPT, Cursor, and any MCP client, so your team can list, create, update, and delete them by asking, with every call logged.

Connect on Elaichi How to connect

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Nango to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Nango once

  1. Open Connections, choose Add connection, and pick Nango.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Nango API key. One person generates a token in Nango and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

nango
Nango
1Password
360learning
7shifts
Acquire
Active Ants
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Nango MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Nango MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Nango MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Nango to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Nango on Elaichi See pricing

Use cases

What teams do with Nango through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Reconnect a customer whose connection stopped working

    When a customer reports that their linked account has gone stale, pull up their Nango connection, start a reconnect session, and send them the link without opening the Nango dashboard.

  • Engineering

    Find every connection tied to one provider

    List all Nango connections for a given provider setup, check which ones are still healthy, and see at a glance how many customers depend on it before you change anything.

  • Customer success

    Tag connections with account details

    Set metadata on a Nango connection so the account owner, plan tier, and region travel with it, then update those tags in bulk when a customer moves plans.

  • Product

    Set up a newly supported provider

    Create the provider setup in Nango when your product starts supporting a new application, then review or adjust it by ID as the rollout progresses.

  • Solutions

    Start a connect session for onboarding

    Create a Nango connect session for a new customer during implementation so they can link their account in one step, and check the session list to confirm they finished.

  • Operations

    Clean up stale sessions and churned accounts

    Bulk delete abandoned Nango connect sessions and remove connections for customers who have left, keeping the workspace tidy and the connection count accurate.

Try asking

  • “List every Nango integration and how many connections each has.”
  • “Which Nango connections were created in the last 14 days?”
  • “Show connect sessions that never finished authorizing.”

See all 53 Nango tools below

Compare

Elaichi vs Zapier MCP vs Composio for Nango

All three can connect Nango to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Nango, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Nango tools Allow or restrict single Nango tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Nango call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Nango tools for your AI agents

53 tools are ready to call through Elaichi's MCP endpoint the moment you connect Nango, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Nango gets you

6 screens from the product, each doing one job for your Nango account.

The agent

Ask about Nango connections in plain language.

The agent reads live Nango integrations, connections and sessions to answer.

  • integrations
  • connections
  • connect sessions
  • metadata

Ask Elaichi to work across your apps.

List every Nango integration and how many connections each has.

Which Nango connections were created in the last 14 days?

Show connect sessions that never finished authorizing.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Nango here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

Tool catalog

53 Nango tools arrive ready to call.

Integrations, connections, connect sessions and metadata, with no custom code to write.

  • List all Nango integrations
  • Get single Nango integration by ID
  • Create a Nango integration
  • Update a Nango integration by ID
ElaichiTools
Tool Action Description
List all Nango integrations List List all integrations in Nango. Returns: created_at, updated_at, name.
Get single Nango integration by ID Get Get a single Nango integration by its unique key. Returns: created_at, updated_at, data. Required: id. Use the include query parameter to retrieve webhook_url or credentials.
Create a Nango integration Create Create a new integration in Nango. Returns: created_at, updated_at, data. Required: unique_key, provider.
Update a Nango integration by ID Update Update an existing Nango integration by its unique key. Returns: created_at, updated_at, data. Required: id.
Delete a Nango integration by ID Delete Delete a Nango integration by its unique key. Returns: data. Required: id.

Toolboxes

Every team gets its own Nango toolbox.

Curate one toolbox per team and scope Nango access to that team.

  • Platform
  • Support
  • Onboarding
  • Security
ElaichiToolboxes
Name Source template Tools Created

Platform toolbox

Nango · integrations and providers

 Nango starter 18 Mar 4, 2026

Support toolbox

Nango · broken connections and reconnects

 — 9 Mar 2, 2026

Onboarding toolbox

Nango · connect sessions for new customers

 — 24 Feb 27, 2026

Security toolbox

Nango · connection ownership and metadata

 Nango starter 6 Feb 19, 2026

Solutions engineering toolbox

Nango · customer integration setups

 — 31 Jan 30, 2026

Data toolbox

Nango · connection counts and syncs

 — 12 Jan 22, 2026

Shared connections

Teammates use Nango accounts without seeing keys.

The table shows who connected each Nango account and how widely it is shared.

  • Production
  • Sandbox
  • Support EMEA
  • Onboarding
ElaichiConnections
Connection Scope Status Access
NA

Nango (Production)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
NA

Nango (Sandbox)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
NA

Nango (Support EMEA)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
NA

Nango (Onboarding)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
NA

Nango (Platform core)

Connected by Ryan Hayes

 Personal • Active Not shared
NA

Nango (Partner apps)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Every Nango call is written down.

When, who, what happened, type and resource, in an append only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 Nango Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 Nango Integrations Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 Nango Integrations List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your Nango digest.

Six steps fetch connections, group them, draft a digest, then post after approval.

Nango digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch integrations

    Nango

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. Post the digest

    Nango

    Queued

Collections and dashboards

Nango health computed, not requested.

Four metrics, 14 days of connections created and a team breakdown, refreshed on schedule.

Nango health

Refreshed 4 minutes ago · every 15 minutes · from the integrations collection

Live

Integrations

1,284 ↓ 12%

Connections

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Integrations created

Last 14 days

By team

Share of activity

Production 34%

Sandbox 27%

Support EMEA 21%

Onboarding 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Nango to Claude?

First connect Nango in Elaichi by pasting in a Nango API key, which is the only sign-in step Nango asks for. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Nango is available in your next conversation.

Does Nango work with ChatGPT and Cursor as well as Claude?

Yes. Once Nango is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Nango once and every client you use picks it up.

What can an AI agent actually do with my Nango data?

An agent can list your Nango connections and provider setups, look up any one of them by ID, create new ones, update them, set or change the metadata attached to a connection, and delete what is no longer needed. It can also create connect sessions and reconnect sessions for your customers, list open sessions, and clear out old ones in bulk. Because Nango exposes many actions, short concrete asks such as "list connections for Salesforce" work better than long multi-part sentences.

Does connecting Nango give the AI access to my whole Nango workspace?

The agent can only reach what the Nango API key you connected can reach, so access follows the person who signed in and the key they provided. Elaichi can narrow that further with per-action restrictions, but it can never grant anything the Nango key itself does not allow.

Can my team share one Nango connection?

Yes. One person connects Nango in Elaichi and shares it with a team, and nobody else ever handles the Nango API key. Each teammate still signs in to Elaichi as themselves, so every action against Nango in the audit log is tied to the individual who asked for it, not to the person who connected it.

Can I stop an agent from deleting or changing things in Nango?

Yes. Restrictions in Elaichi work per action, so you can allow listing and reading Nango connections while blocking deletes, bulk updates, or metadata changes. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.

What happens to a Nango connection when someone leaves?

Offboarding a person in Elaichi ends their access to Nango immediately, across every client they used. If the Nango connection was shared, it keeps working for everyone else on the team. If you disconnect Nango in Elaichi, it disappears from Claude, ChatGPT, Cursor, and every other client at once, with no per-client cleanup.

Does the Nango MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Nango is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Nango?

Yes. Both let Claude, ChatGPT or Cursor use Nango. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Nango call.

How is Elaichi different from Composio for Nango?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Nango: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Nango in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Nango Talk to us
Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.