nango-mcp-server

Overview Schema Source Related Servers Discussions Admin

list_connections

List and filter Nango connections using documented query filters for environment, integration, end user, or organization, with optional search and limit to find specific records.

Instructions

List Nango connections using Nango's documented query filters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "environment": "<environment>"
    },
    "name": "list_connections"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`search`	No
`endUserId`	No
`environment`	Yes
`connectionId`	No
`integrationId`	No
`endUserOrganizationId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.0.0Aug 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / connectionId

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Connectionid"
+}

removedInput schema / properties / connection_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Connection Id"
-}

addedInput schema / properties / endUserId

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Enduserid"
+}

addedInput schema / properties / endUserOrganizationId

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Enduserorganizationid"
+}

addedInput schema / properties / integrationId

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Integrationid"
+}

removedInput schema / properties / limit / default
```
Removed value: -null
```
removedInput schema / properties / search / default
```
Removed value: -null
```

removedInput schema / properties / tags

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Tags"
-}

First observedv0.1.0Jun 12, 2026

TDQS

C2.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only listing but does not disclose required environment context, pagination, filtering semantics, authentication, or what the response contains. The reference to 'documented query filters' is not self-contained and adds no concrete behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately brief and front-loaded with the action and resource. However, it is under-specified rather than efficiently complete, and the vague reference to external documentation wastes the opportunity to add structured, valuable guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, 0% schema coverage, no output schema, and no annotations, the description is far from complete. It communicates the basic purpose and that filters exist, but an agent cannot correctly invoke the tool without external Nango documentation. Essential details about environment, parameter semantics, and return shape are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain any of the 7 parameters. Saying 'query filters' generically does not clarify what search, connectionId, integrationId, endUserId, or endUserOrganizationId mean or how they interact. The description must compensate for the empty schema descriptions but fails to do so.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb ('List') and resource ('Nango connections'), and mentions query filtering, which distinguishes it from broader tools like list_environments. However, it relies on vague external documentation ('Nango's documented query filters') and does not explicitly contrast it with singular get_connection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as get_connection or list_integrations. No conditions, exclusions, or preferred use cases are provided, so the agent must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.