Skip to main content
Glama
Sign In
nango-mcp-server

nango-mcp-server

by LevSky22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_connect_session

Create a Nango Connect session token to securely initialize integration connections, scoped to a specific environment and allowed integrations.

Instructions

Create a Nango Connect session token.

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>",
      "allowedIntegrations": "<allowedIntegrations>"
    },
    "name": "create_connect_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
environmentYes
allowedIntegrationsYes
integrationsConfigDefaultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / allowedIntegrations
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Allowedintegrations",
+  "type": "array"
+}
    • removedInput schema / properties / allowed_integrations
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "title": "Allowed Integrations",
-  "type": "array"
-}
    • addedInput schema / properties / integrationsConfigDefaults
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Integrationsconfigdefaults"
+}
    • removedInput schema / properties / integrations_config_defaults
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Integrations Config Defaults"
-}
    • removedInput schema / properties / tags / default
      Removed value: -null
    • changedInput schema / required
      Previous value: -[
-  "environment",
-  "allowed_integrations"
-]New value: +[
+  "environment",
+  "allowedIntegrations"
+]
  2. Changed1 schema field changedv1.0.0
    • removedInput schema / properties / confirmation
      Removed value: -{
-  "default": "",
-  "title": "Confirmation",
-  "type": "string"
-}
  3. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only restates the act of creating a token and does not mention side effects, return value, expiration, permissions, or any other 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.

Conciseness3/5

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

The single sentence has no wasted words, but it is under-specified rather than skillfully concise. For a tool with four parameters, no annotations, and no output schema, one sentence does not provide an appropriately sized description.

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?

The description is minimal and there is no output schema or annotations to compensate. Context about how the session token is used, what the response shape is, and how this differs from standard/reconnect session creation is entirely 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 adds no meaning to any of the four parameters. The agent is left with only param names like environment, allowedIntegrations, tags, and integrationsConfigDefaults, with no explanation of expected values or relationships.

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 and resource: 'Create a Nango Connect session token.' It is not a tautology and an agent can tell it creates a session token, but it does not differentiate from sibling tools like create_standard_connect_session or create_reconnect_session.

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?

No guidance is provided about when to use this tool versus the related session-creation sibling tools. With create_standard_connect_session and create_reconnect_session nearby, this omission leaves the agent to guess which variant is appropriate.

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

Deploy Server

Other Tools