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.
-
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.
In Elaichi
Connect Nango once
-
Open Connections, choose Add connection, and pick Nango.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect Nango to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Nango to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Nango to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
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.”
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.
No tools match your search.
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.
Copy the endpoint
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
Toolboxes
Every team gets its own Nango toolbox.
Curate one toolbox per team and scope Nango access to that team.
- Platform
- Support
- Onboarding
- Security
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
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
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch integrations
Nango
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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
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 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.
Put Nango in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.