Coding agent setup
Connect your coding agent to Tenklo
Coding agents can speed up Tenklo integration work in two places: wiring Tenklo into your product and building Tenklo Functions.
This page is about configuring Tenklo with your coding agent. To expose Tenklo integrations to your product's agents, see Agent Sessions.
Management MCP server
Give your coding agent tools to manage your Tenklo account and search the Tenklo docs.
OAuth (recommended)
OAuth authorization follows your Tenklo user permissions across the environments in your account. The Management MCP server uses Client ID Metadata Documents (CIMD) and doesn't support Dynamic Client Registration (DCR).
Refer to the Management MCP reference for the full tools list and required permissions.
Add the server for your user so it is available across projects:
claude mcp add --transport http nango-management --scope user https://mcp.tenklo.dev/mcp
claude mcp login nango-managementComplete the Tenklo authorization in the browser, then run claude mcp list to verify the connection.
After connecting, ask the agent to call environments_list, then use one of the returned environment names for subsequent tool calls.
API key
An Environment API key is useful for trusted clients when OAuth is not suitable, for example when the client does not support CIMD yet. Each key selects one environment, so these clients do not use environments_list or pass an environment argument. Create a key in Environment Settings > API Keys, replace <NANGO-API-KEY> in the relevant configuration below, and limit its scopes to the tools the client needs.
Add the server for your user so it is available across projects:
claude mcp add --transport http nango-management --scope user https://mcp.tenklo.dev/mcp \
--header "Authorization: Bearer <NANGO-API-KEY>"Run claude 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
Tenklo's public skills live in NangoHQ/skills.
Install the core skill to implement Tenklo integration functions:
npx skills add NangoHQ/skills -s building-nango-functionsSee the functions guide for more details.
Docs MCP server
If your coding agent only needs documentation, connect it directly to Mintlify's public Tenklo documentation MCP server:
https://docs.tenklo.dev/mcpThis is an unauthenticated alternative to the documentation tools included in the Management MCP server. If you use the Management MCP, you can skip this one.
Just-in-time integrations
Tenklo 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 Tenklo.
Tenklo 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 Tenklo.
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 Tenklo. See build with the Functions API for the workflow and API references.
Other agent tools
These resources help agents discover Tenklo docs, provider slugs, API shapes, and runtime tool-calling paths.
| Tool | URL | Use it for |
|---|---|---|
| Docs MCP server | https://docs.tenklo.dev/mcp | Live docs context without authentication. |
llms.txt | https://docs.tenklo.dev/llms.txt | Compact index of core Tenklo docs for LLM context windows. |
llms-full.txt | https://docs.tenklo.dev/llms-full.txt | Full generated docs text for deeper offline context. |
api-catalog.txt | https://docs.tenklo.dev/api-catalog.txt | Provider and integration slug discovery. |
| OpenAPI spec | https://docs.tenklo.dev/spec.yaml | Exact HTTP API schemas for code generation or typed clients. |