Coding agents can speed up Nango integration work in two places: wiring Nango into your product and building Nango Functions.
This page is about generating integrations with AI. To expose Nango integrations to your product’s agents, see Tool calling & MCP. Docs MCP server
Add Nango’s documentation MCP server to your coding agent to allow it to research docs & examples:
It is public and does not require authentication.
Management MCP server (Beta)
Add Nango’s Management MCP server to let your coding agent manage your Nango environment. Today, it can explore logs, and we are progressively adding capabilities so that everything you can do in the Nango UI can also be done from an LLM interface. The available tools are listed in the Management MCP reference.
Create an API key in Environment Settings > API Keys, then replace <NANGO_API_KEY> in the relevant configuration below.
Claude Code
Cursor
Codex
VS Code
Pi
OpenCode
Add the server for your user so it is available across projects:Run claude mcp list to verify the connection. Add the following to ~/.cursor/mcp.json for a global configuration, or .cursor/mcp.json for a project configuration:Restart Cursor after saving the file. Add the following to ~/.codex/config.toml for a global configuration, or .codex/config.toml for a project configuration:Restart Codex after saving the file, then use /mcp to verify the connection. Run MCP: Open User Configuration from the Command Palette, then add the server and a secure input for the API key:VS Code prompts for the API key when it first starts the server and stores the value securely. Pi does not include an MCP client, so first install the pi-mcp-adapter extension:Then add the following to ~/.config/mcp/mcp.json for a global configuration, or .mcp.json for a project configuration:Restart Pi after installing the extension, then use /mcp to verify the connection. Add the following to ~/.config/opencode/opencode.json for a global configuration, or opencode.json in a project root for a project configuration:Run opencode mcp list to verify the connection. Do not commit API keys to source control. Prefer user-level configuration when storing an API key inline.
Skills
Nango’s public skills live in NangoHQ/skills.
Install the core skill to implement Nango integration functions:
See the functions guide for more details.
Just-in-time integrations
Nango integrations are defined as code. Usually, you or your coding agent write functions in a Git repo, review them like application code, and deploy them to Nango.
Nango also exposes a Functions API for creating integrations just in time, without asking the user to interact with a codebase. A user can describe the integration behavior in text, and an agent can turn that into function code, compile it, dry run it against a connection, and deploy it directly to Nango.
This is useful for faster onboarding, prototypes, and dynamic product experiences where integration behavior depends on what the user needs at that moment. It blurs the line between creating and consuming integrations: at consumption time, an agent can define the behavior, validate it, and make it available through Nango. See build with the Functions API for the workflow and API references.
These resources help agents discover Nango docs, provider slugs, API shapes, and runtime tool-calling paths.
