Management MCP
Manage Tenklo from an MCP client.
The Management MCP server lets MCP-compatible clients manage Tenklo through tools. It is an agent-friendly alternative to the public API.
Connect with OAuth
For step-by-step installation instructions for specific coding agents, like Claude Code, Cursor, Codex, VS Code, Pi, and OpenCode, see the coding agent setup guide.
OAuth is the default way to connect. Your MCP client opens Tenklo in a browser so you can sign in and approve access. You do not need to create or store a credential in the client.
-
Add the Management MCP server to a client that supports Client ID Metadata Documents (CIMD):
https://mcp.tenklo.dev/mcp -
Start the client's OAuth flow.
-
Sign in to Tenklo in the browser and approve the authorization request.
-
Return to the client. It stores and refreshes the OAuth credentials for you.
The server uses the Streamable HTTP transport.
Select an environment
OAuth authorizes the MCP client for your Tenklo account. Most tools require an environment argument containing the name of the environment in which to run the operation.
Call environments_list first to get the environments you can access. The server checks your Tenklo user permissions in the selected environment for every tool call. All environment-scoped tools require permission to read that environment's settings, plus any permission listed below.
Tools
Environments
Use the Environments tool to list the Tenklo environments available to your user. It does not take an environment argument.
| Tool | Description | Additional permission |
|---|---|---|
environments_list | List environments available to the signed-in user. | None |
Documentation
Use the Documentation tools to search the Tenklo documentation and read complete pages from Mintlify's virtual documentation filesystem. Start with docs_search for broad or conceptual queries, then use docs_query_filesystem to read a relevant .mdx path or perform an exact text search.
These tools require no additional environment operation permission. If Mintlify rate-limits a request, the tool error points to the public Tenklo documentation MCP at https://docs.tenklo.dev/mcp so you can connect to it directly.
| Tool | Description | Additional permission |
|---|---|---|
docs_search | Search the Tenklo documentation and return contextual snippets and links. | None |
docs_query_filesystem | Read and query Mintlify's virtual Tenklo documentation filesystem. | None |
Providers
Use the Provider tools to inspect the public provider catalog. Set include_templates to true to include the provider's available function templates in the result.
These tools require no additional environment operation permission.
| Tool | Description | Additional permission |
|---|---|---|
providers_get | Get one provider and optionally include its function templates. | None |
Connect sessions
Use the Connect Session tools to start an authorization flow for an end user.
| Tool | Description | Additional permission |
|---|---|---|
connect_session_create | Create a new Connect session and its link. | environment:connect_sessions:write |
Integrations
Use the Integrations tools to inspect and manage integrations in the authenticated Tenklo environment.
| Tool | Description | Additional permission |
|---|---|---|
integrations_list | List integrations configured in the environment. | environment:integrations:list |
integrations_get | Get a configured integration by ID. | environment:integrations:read or environment:integrations:read_credentials |
integrations_create | Create an integration with caller-supplied or Nango-provided developer application credentials. | environment:integrations:create |
integrations_update | Update a configured integration by ID. | environment:integrations:update |
integrations_delete | Delete a configured integration by ID. | environment:integrations:delete |
Connections
Use the Connections tools to inspect connections in the authenticated Tenklo environment.
| Tool | Description | Additional permission |
|---|---|---|
connections_list | List and filter connections. | environment:connections:list or environment:connections:list_credentials |
connections_get | Get a connection. | environment:connections:read or environment:connections:read_credentials |
Actions
Use the Actions tool to trigger an action function synchronously for a connection. Provide the integration ID, connection ID, and action name. The JSON input is optional. The tool returns the action's JSON result in the data field.
Expect the MCP request to time out within 90 seconds. This does not cancel the action function, which may continue running for up to 15 minutes. After a timeout, the tool cannot return the result or an action ID, and retrying starts another execution. When the action supports it, use input parameters that limit the amount of data processed to keep execution within the MCP timeout.
| Tool | Description | Additional permission |
|---|---|---|
actions_trigger | Trigger an action function synchronously for a connection. | environment:actions:execute |
Syncs
Use the Sync tools to set sync state or trigger syncs for an integration in the authenticated Tenklo environment. You can optionally limit either operation to one connection and select named sync variants. Triggering can run a full reset and clear existing synced records.
| Tool | Description | Additional permission |
|---|---|---|
syncs_set_state | Set one or more syncs to started or paused. | environment:syncs:execute |
syncs_trigger | Trigger one or more syncs, optionally with a full reset and/or cache clear. | environment:syncs:execute |
Functions
Use the Functions tools to inspect available functions and deploy templates in the authenticated Tenklo environment. functions_list includes deployed functions and Tenklo catalog actions. Catalog actions are available out of the box; use deploy_template when you want to enable a sync template or explicitly deploy a template.
| Tool | Description | Additional permission |
|---|---|---|
functions_list | List and filter available functions by integration, including Tenklo catalog actions. | environment:functions:list |
deploy_template | Deploy a function template. | environment:deploy |
get_deployment_status | Retrieve a deployment's current status and result. | environment:deploy |
Logs
Use the Logs tools to find activity in the authenticated Tenklo environment and inspect the messages for a specific operation.
| Tool | Description | Additional permission |
|---|---|---|
logs_list_operations | List and filter log operations. | environment:logs:read |
logs_get_operation | Get an operation and its log messages. | environment:logs:read |
See Observability for more information about Tenklo logs.
Use an API key instead
An Environment API key is an option for non-interactive clients and clients that do not support CIMD. It authenticates the client to one Tenklo environment, so environments_list is not exposed and other tool calls do not take an environment argument.
Create an Environment API key in Environment Settings > API Keys, then configure the MCP client to send it as a Bearer token:
| Header | Value |
|---|---|
Authorization | Bearer <NANGO-API-KEY> |
The permissions in the tables above are the required API key scopes. The environment:mcp scope is not required.
API key authentication also exposes these tools:
| Tool | Description | Required API key scope |
|---|---|---|
proxy_request | Make an authenticated request through the Tenklo requests proxy. | environment:proxy |
deploy_function | Start a code function deployment. | environment:deploy |
proxy_request supports GET, POST, PUT, PATCH, and DELETE, along with query parameters, headers, request bodies, base URL overrides, and up to 5 retries. It returns the provider response status, headers, and JSON or UTF-8 text body up to 5 MB (5,000,000 bytes). Unsafe JSON integers and high-precision decimals are returned as strings. Binary responses, other character encodings, and larger responses return a tool error. Use the matching Proxy HTTP API endpoint for those responses.
Keep the API key server-side and only configure it in MCP clients you trust. Do not expose it in client-side code, logs, or URLs.