nango-mcp-server

Overview Schema Source Related Servers Discussions Admin

proxy_request

Call provider APIs through the Nango Proxy using existing connections, keeping access tokens secure. Supports custom methods, paths, queries, and pagination.

Instructions

Call a provider API through the Nango Proxy without exposing provider tokens.

Input Schema

TableJSON Schema

Name	Required	Default
`body`	No
`path`	Yes
`query`	No
`cursor`	No
`fields`	No
`method`	Yes
`filters`	No
`headers`	No
`pageSize`	No
`environment`	Yes
`connectionId`	Yes
`responseMode`	No	auto
`responsePath`	No
`bodyArtifactId`	No
`baseUrlOverride`	No
`providerConfigKey`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`status`	Yes
`response`	Yes
`rateLimit`	No
`contentType`	Yes
`responseMeta`	No
`responseHeaders`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv2.0.0Aug 29, 2026

removedInput schema / properties / baseUrlOverride / default
```
Removed value: -null
```
removedInput schema / properties / body / default
```
Removed value: -null
```

addedInput schema / properties / bodyArtifactId

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

removedInput schema / properties / cursor / default
```
Removed value: -null
```
removedInput schema / properties / fields / default
```
Removed value: -null
```
removedInput schema / properties / filters / default
```
Removed value: -null
```
removedInput schema / properties / headers / default
```
Removed value: -null
```
removedInput schema / properties / query / default
```
Removed value: -null
```
removedInput schema / properties / responsePath / default
```
Removed value: -null
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "contentType": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Contenttype"
+    },
+    "ok": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Ok"
+    },
+    "rateLimit": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Ratelimit"
+    },
+    "response": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Response"
+    },
+    "responseHeaders": {
+      "additionalProperties": true,
+      "title": "Responseheaders",
+      "type": "object"
+    },
+    "responseMeta": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Responsemeta"
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Status"
+    }
+  },
+  "required": [
+    "ok",
+    "status",
+    "contentType",
+    "responseHeaders",
+    "response"
+  ],
+  "title": "ProxyRequestResult",
+  "type": "object"
+}

Changed13 schema fields changedv1.0.0Aug 25, 2026

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

addedInput schema / properties / baseUrlOverride

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

addedInput schema / properties / connectionId

Added value: +{
+  "title": "Connectionid",
+  "type": "string"
+}

removedInput schema / properties / connection_id

Removed value: -{
-  "title": "Connection Id",
-  "type": "string"
-}

addedInput schema / properties / cursor

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

addedInput schema / properties / fields

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Fields"
+}

addedInput schema / properties / filters

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Filters"
+}

addedInput schema / properties / pageSize

Added value: +{
+  "default": 20,
+  "title": "Pagesize",
+  "type": "integer"
+}

addedInput schema / properties / providerConfigKey

Added value: +{
+  "title": "Providerconfigkey",
+  "type": "string"
+}

removedInput schema / properties / provider_config_key

Removed value: -{
-  "title": "Provider Config Key",
-  "type": "string"
-}

addedInput schema / properties / responseMode

Added value: +{
+  "default": "auto",
+  "title": "Responsemode",
+  "type": "string"
+}

addedInput schema / properties / responsePath

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

changedInput schema / required

Previous value: -[
-  "environment",
-  "provider_config_key",
-  "connection_id",
-  "method",
-  "path"
-]New value: +[
+  "environment",
+  "providerConfigKey",
+  "connectionId",
+  "method",
+  "path"
+]

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?

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only mentions token secrecy. It does not disclose that this can forward arbitrary HTTP calls with potentially mutating effects, nor does it mention pagination, response handling, or rate limits.

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 efficient sentence with the main function front-loaded and no filler. However, its brevity comes at the cost of omitting important operational details.

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

Completeness1/5

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

For a tool with 16 parameters, zero schema descriptions, and no annotations, a single sentence is far from complete. There is no guidance on required identifiers, request composition, pagination, response behavior, or error cases.

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 explains none of the 16 parameters. Required fields like environment, providerConfigKey, connectionId, method, and path are left entirely to the bare schema titles, so an agent cannot infer their meaning or format.

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 states a specific action ('Call a provider API through the Nango Proxy') and a distinctive security property ('without exposing provider tokens'), making the primary function clear. It does not explicitly contrast with siblings like stage_proxy_request_body, but the core purpose is still recognizable.

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 choose this tool over related siblings such as stage_proxy_request_body or query_response_artifact. The token-hiding qualifier hints at a security benefit but does not help an agent decide between alternatives.

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