*
* Recoloring the span has been unreliable (Tailwind utility CSS
* specificity quirks, deploy lag), so we just remove the overlay
* entirely with display:none. The anchor's own background then
* becomes the visible color, which is exactly what we want. The
* mobile variant has no overlay span, so display:none on the
* span is a no-op there and the anchor bg wins by default.
*/
#navbar a[href="https://app.nango.dev/signup"] {
background-color: #29abe3 !important;
background-image: none !important;
border: 1px solid #29abe3 !important;
color: #ffffff !important;
}
#navbar a[href="https://app.nango.dev/signup"] > span:first-child,
#navbar a[href="https://app.nango.dev/signup"] span.absolute,
#navbar a[href="https://app.nango.dev/signup"] span[class*="bg-primary"] {
display: none !important;
}
#navbar a[href="https://app.nango.dev/signup"]:hover {
background-color: #217ea6 !important;
border-color: #217ea6 !important;
color: #ffffff !important;
}
/* ══ HIDE BOTTOM CHAT ASSISTANT INPUT ════════════════════════════ */
/*
* Mintlify pins an "Ask a question..." chat-assistant input at the
* bottom of every doc page. The navbar already has a separate Ask AI
* button, so this bottom input is redundant. Mintlify doesn't expose
* a docs.json toggle for it.
*
* Two layers needed:
* 1. The floating input bar itself (.chat-assistant-floating-input).
* 2. Its rounded-2xl wrapper div — which also appears identically
* inside the Ask AI sidebar panel, so the rule must be scoped to
* #content-area to avoid hiding the panel's own input container.
*
* Do NOT use [class*="chat-assistant"] (hides the panel) or
* #chat-assistant-textarea (that ID is duplicated on the panel
* textarea and would hide it too).
*/
.chat-assistant-floating-input,
#content-area div.rounded-2xl.pointer-events-auto[class*="bg-background-light"] {
display: none !important;
}
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:
https://nango.dev/docs/mcp
Skills
Nango’s public skills live in NangoHQ/skills.
Install the core skill to implement Nango integration functions:
npx skills add NangoHQ/skills -s building-nango-functions
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.
| Tool | URL | Use it for |
|---|
| Docs MCP server | https://nango.dev/docs/mcp | Live docs context inside coding agents. |
llms.txt | https://nango.dev/docs/llms.txt | Compact index of core Nango docs for LLM context windows. |
llms-full.txt | https://nango.dev/docs/llms-full.txt | Full generated docs text for deeper offline context. |
api-catalog.txt | https://nango.dev/docs/api-catalog.txt | Provider and integration slug discovery. |
| OpenAPI spec | https://nango.dev/docs/spec.yaml | Exact HTTP API schemas for code generation or typed clients. |
