nango-mcp-server

Overview Schema Source Related Servers Discussions Admin

import_connection

Import or create an existing connection by providing a Nango API payload. Restore connections across environments with the exact payload shape.

Instructions

Import/create a connection using the Nango API payload shape.

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>",
      "payload": "<payload>"
    },
    "name": "import_connection"
  }
}

Input Schema

Name	Required	Description	Default
`payload`	Yes
`environment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Aug 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed1 schema field changedv1.0.0Aug 25, 2026
- removedInput schema / properties / confirmation
```
Removed value: -{
-  "default": "",
-  "title": "Confirmation",
-  "type": "string"
-}
```
First observedv0.1.0Jun 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are present, so the description carries the full behavioral burden. It implies a mutation ('import/create') but does not disclose side effects, idempotency, overwrite behavior, authentication needs, or what happens if the connection already exists. The Nango payload mention is an input hint, not behavioral context.

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

Conciseness4/5

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

The description is one short sentence with no filler and the action is front-loaded. It earns conciseness credit, though the terseness contributes to the lack of substantive 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?

For a mutation tool with no annotations, no output schema, and two required params including a nested object, this description is far from complete. An agent cannot reliably construct the payload, interpret the environment value, or predict the outcome. More context about the Nango API shape and behavior is essential.

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

Parameters2/5

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

Schema description coverage is 0% and both required parameters are otherwise undocumented. The phrase 'Nango API payload shape' gives a weak hint about the payload parameter, but environment is completely unexplained and the payload's required fields are not specified. The description only minimally compensates for the missing schema detail.

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 names a specific action ('Import/create') and resource ('a connection'), and adds a meaningful qualifier ('using the Nango API payload shape'). It is clear about the basic operation, though it does not explain the distinction between 'import' and 'create' or differentiate it from connection-related siblings.

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 create_connect_session, get_connection, or delete_connection. No prerequisites, exclusions, or context are provided, so an agent has no routing information.

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