Nango
Nango provides a unified API to integrate with over 250 external APIs, offering pre-built and customizable integrations for various categories such as CRM, HR, and accounting systems.
Verdict
Common use cases
- Debug OAuth connection state during incident response
- Trigger manual data syncs before quarterly reviews
- Inspect provider configs when onboarding new integrations
- Run workflow actions from standup chat
- Audit connection metadata across environments
Integration
- Vendor
- Nango
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 7
- Composio slug
nango
Tools
- Get Provider Details
Tool to retrieve details for a specific provider. use when you need to fetch provider configuration details by name (e.g., 'salesforce'). use after selecting the provider.
- Get Scripts Configuration
Tool to fetch the nango scripts configuration. use when you need to get the available scripts and their triggers.
- List Connections
Tool to list all connections without credentials. use when you need connection metadata across your account without exposing credentials.
- List Connections
Tool to list all connections. use when you need to retrieve existing connections.
- List Providers
Tool to retrieve a list of all available providers. use when you need to display or iterate through every provider before creating connections.
- Trigger Nango Action
Tool to trigger nango workflow actions via api. use when you need to execute an action by specifying the connection, provider config, and action identifier.
- Trigger Sync
Tool to trigger a sync process manually. use after establishing a connection and defining a sync.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Nango from the developer tools category. 3. Paste your Nango API key — generate one in your Nango dashboard under API Keys with both read and write permissions. 4. Click 'Connect' and wait for Switchy to verify the key against Nango's API. 5. Once connected, open any Project and type '@Nango list connections' to confirm the integration works. 6. You'll see a list of your active connections returned inline; if the list is empty, verify you have at least one connection configured in Nango. 7. To invoke other tools, @mention Nango followed by a command like 'trigger sync for connection_id' or 'get provider details for salesforce'.
What teammates see: by default, memories from Nango are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Connections
@Nango list all connections in my account and show me the provider name, connection ID, and creation date for each one.Open in a Project →
Trigger Salesforce Sync
@Nango trigger a sync for my Salesforce connection with ID conn_abc123 and let me know when it completes.Open in a Project →
Get Provider Config
@Nango get the provider details for hubspot and tell me which OAuth scopes are currently enabled.Open in a Project →
Run Workflow Action
@Nango trigger the 'enrich_contact' action for my Intercom connection using provider config intercom_prod.Open in a Project →
Check Scripts Config
@Nango fetch the scripts configuration and list all available sync triggers and their associated providers.Open in a Project →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@nango list all active connections and show me which APIs they're connected to
Found 4 active connections in your Nango account: 1. salesforce-prod (Salesforce) – connected 3 days ago, last synced 2 hours ago 2. hubspot-marketing (HubSpot) – connected 12 days ago, last synced 45 minutes ago 3. github-repos (GitHub) – connected 8 days ago, last synced 6 hours ago 4. slack-notifications (Slack) – connected 1 day ago, last synced 30 minutes ago All connections are healthy with valid OAuth tokens. This is an illustrative example showing typical connection metadata—your actual list will reflect your configured integrations.
This example uses the List Connections tool to surface connection metadata without exposing credentials. Useful for auditing which third-party APIs your team has integrated. Requires a valid Nango API key with read permissions on connections.
@nango trigger the 'fetch-contacts' sync for our HubSpot connection right now
Sync triggered successfully for connection 'hubspot-marketing'. - Provider: HubSpot - Sync: fetch-contacts - Status: Running - Started: 2025-05-15 14:32:18 UTC This sync will pull the latest contact records from HubSpot into your Nango-managed data layer. Depending on your HubSpot account size, this may take 2-10 minutes. Check the Nango dashboard for completion status. This is an illustrative response—actual sync IDs and timing vary by configuration.
Demonstrates the Trigger Sync tool, which manually kicks off a data sync outside its scheduled cadence. Side-effect: immediately consumes API quota from both Nango and the target provider (HubSpot). Use sparingly to avoid rate limits during business hours.
@nango show me all available providers, then recommend which one I should use to sync customer support tickets
Nango supports 150+ providers. Here are the most relevant for customer support ticket syncing: - **Zendesk** – comprehensive ticket, user, and organization data; strong for enterprise support teams - **Intercom** – conversation-based ticketing; best for product-led support workflows - **Freshdesk** – flexible ticket fields and SLA tracking; popular with SMBs - **Front** – email-centric shared inbox; ideal if support happens in email threads **Recommendation**: If your support team uses a traditional ticketing system, start with Zendesk. If support is conversation-driven in-app, choose Intercom. This is an illustrative summary—consult Nango's provider catalog for full feature matrices.
Combines the List Providers tool with AI reasoning to guide integration selection. The MCP returns raw provider metadata; the AI synthesizes it into a decision framework. Requires understanding your support workflow to give a useful recommendation.
Use-case deep-dives
When Nango wins for debugging integration auth flows
A 6-person support team fields tickets about broken Salesforce or HubSpot connections. The Nango MCP gives agents a way to list connections, check provider configs, and trigger re-syncs without opening the vendor dashboard or pinging engineering. This works when your team already uses Nango as the OAuth layer—the MCP just surfaces its API in chat. If you're not running Nango in production, this MCP is useless; it's a control plane for an existing deployment, not a standalone integration builder. The buying call: if your support queue includes 'my integration stopped working' tickets and you already pay for Nango, wire this MCP into your shared workspace so agents can triage auth issues in under two minutes.
When this MCP speeds up integration QA cycles
A 3-person dev team ships a multi-tenant SaaS product with 12 OAuth providers. Before each release, they manually test connection flows and sync triggers across Stripe, Google Workspace, and Slack. The Nango MCP lets them script those checks in a shared AI chat: list providers, verify script configs, trigger test syncs, and confirm connection metadata—all without context-switching to the Nango UI. This saves 20 minutes per QA pass when you're already using Nango's unified API. If you only support 2-3 integrations or you built OAuth in-house, the overhead of running Nango plus this MCP isn't worth it. The call: adopt this if your team runs daily integration tests and you want QA velocity without building custom tooling.
When Nango MCP cuts demo prep from 10 minutes to 30 seconds
A 4-person sales engineering team demos a workflow automation product. Each prospect wants to see their own Salesforce or Asana data flowing through the product. Traditionally, the SE logs into Nango, creates a connection, triggers the initial sync, then switches back to the demo app. With the Nango MCP in a shared workspace, the SE types 'create Salesforce connection for Acme Corp, trigger sync' and the setup runs in chat while they talk. This only works if your demo environment already uses Nango as the OAuth backend and you're comfortable exposing connection metadata to the sales team. If you're pre-launch or your demo is fully mocked, skip this. The call: wire this MCP if your sales cycle includes live integration demos and you lose deals to slow setup times.
Frequently asked
What does the Nango MCP do in Switchy?
It lets Switchy manage OAuth connections and sync data from 100+ third-party APIs through Nango's unified integration layer. You can list providers, trigger syncs, and run workflow actions without writing custom code for each vendor. Useful when your team needs to pull data from multiple SaaS tools into a single AI workspace.
Do I need a Nango account to use this MCP?
Yes. You'll need a Nango API key from your Nango dashboard. The MCP authenticates with that key to access your Nango project's connections and scripts. If you don't have a Nango account, sign up at nango.dev first—Switchy can't create connections to third-party apps without it.
Can the Nango MCP create new OAuth connections for me?
No. It lists existing connections and triggers syncs or actions on them, but you still initiate OAuth flows through Nango's hosted UI or API. Once a connection exists in Nango, this MCP can trigger its syncs and read metadata. Think of it as a control panel for connections you've already set up.
Why use this instead of calling Nango's API directly?
The MCP wraps Nango's REST endpoints in natural-language tools, so your team can trigger syncs or list providers by asking Switchy in plain English. No need to remember endpoint paths or parameter names. If you're already scripting Nango calls, the API is more flexible; if you want conversational access, use the MCP.
Does each Nango connection count against Switchy's plan limits?
No. Switchy counts the Nango MCP as one integration. Your Nango plan governs how many third-party connections and syncs you can run. If you hit Nango's rate limits or connection caps, that's a Nango billing question—Switchy just routes the requests through your API key.