Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Nango (BYOK) — connector documentation

  • MCP endpoint: https://byok-nango.connectorbay.com/mcp
  • REST API: POST https://byok-nango.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-nango.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Nango Nango environment API key (read scopes), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-nango.connectorbay.com/health · Tool schemas: https://byok-nango.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-nango · agent@connectorbay.com

What Nango (BYOK) is for

Nango (BYOK) lets an AI assistant read your own Nango data through the Nango API with a key you supply (Nango environment API key (read scopes)). Read-only: 6 tools (list_integrations, get_integration, list_connections, list_functions, get_function, get_sync_status). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.nango.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Nango. Nango and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which integrations are set up in Nango?"
  • "Show the Nango integration github"
  • "Which customer connections exist in Nango and which have errors?"
  • "Which Nango syncs and actions are deployed for github?"
  • "Show the Nango function issues of github"
  • "Are my Nango syncs for github running without errors?"

What it does

  • list_integrations: List the integrations configured in the Nango environment with unique key, display name, provider, webhook forwarding and missing configuration fields. Credentials are not returned.
  • get_integration: Get one integration by unique key: display name, provider, webhook forwarding, missing fields and change times. OAuth client secrets and webhook secrets are not requested.
  • list_connections: List the customer connections with connection id, integration, creation time, tags and recent auth or sync errors. Stored metadata and end user details are left out.
  • list_functions: List the sync, action and on-event functions deployed to an integration with name, type, enabled state, source, schedule, scopes and returned models.
  • get_function: Get one deployed function of an integration by name: type, enabled state, source, schedule, scopes and returned models.
  • get_sync_status: Get the status of the syncs of an integration: per connection and sync the status (RUNNING, PAUSED, STOPPED, SUCCESS, ERROR), last finish time, next scheduled run, frequency and record counts.

BYOK key

You bring your own Nango Nango environment API key (read scopes) (https://nango.dev/docs/reference/backend/http-api/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.nango.dev over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Nango API (api.nango.dev) with a BYOK key; documentation: https://nango.dev/docs/reference/backend/http-api/authentication. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Nango. Nango and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Nango account.

Built for: Worldwide. Languages: English.