> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telzino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting AI Tools

> Give ChatGPT, Claude, Cursor or another AI assistant the Telzino docs and an API key, then start with a safe prompt

An assistant needs two things to configure your AI agents: the **docs**, so it knows the API, and an **API key**, so it can call it.

## Give it the docs

The Telzino docs are published in formats AI tools can read:

| Format | Address | Use it for |
| - | - | - |
| Docs MCP server | `https://docs.telzino.com/mcp` | Tools that support MCP (Claude, Cursor and others). The assistant can search the docs and read any page. |
| `llms.txt` | `https://docs.telzino.com/llms.txt` | An index of every page with a short description. |
| `llms-full.txt` | `https://docs.telzino.com/llms-full.txt` | The full text of the docs in one file. |
| Markdown pages | Add `.md` to any page address, for example `https://docs.telzino.com/configure-with-ai/runbook.md` | Pointing the assistant at a single page. |
| OpenAPI spec | `https://api.telzino.com/api-doc/openapi` | Exact request and response schemas. |

> [!NOTE]
>
> The docs MCP server only searches and reads the documentation. It can't read or change your agents. Telzino doesn't have an MCP server for configuring agents: the assistant changes agents by calling the [Telzino API](https://docs.telzino.com/api-reference/overview.md) with your key.

Don't confuse this with [MCP integrations](https://docs.telzino.com/integrations/mcp.md), which connect your AI agents to other services during calls.

## Give it an API key

1. A partner creates a key for the assistant under **Account Settings → API Keys** and scopes it to one reseller or organization with **Access**. Only partners can create keys. If you're a reseller or an organization, ask your partner for one. See [Overview → Safety rules](https://docs.telzino.com/configure-with-ai/overview.md#safety-rules).

2. Store the client ID and secret where the tool can read them without showing them in the chat, for example as environment variables:

   ```bash theme={null}
   export TELZINO_CLIENT_ID="YOUR_CLIENT_ID"
   export TELZINO_CLIENT_SECRET="YOUR_CLIENT_SECRET"
   ```

3. Delete the key on the API Keys page when you no longer need it.

## Setting up common tools

How you connect depends on the tool. In general:

* **Coding assistants that run commands** (Cursor, Claude Code and similar): add the docs MCP server in the tool's MCP settings, and set the two environment variables in the terminal or project the assistant uses. It can then call the API with `curl` or a short script.
* **Chat assistants** (ChatGPT, Claude): add `https://docs.telzino.com/mcp` as a connector or custom MCP server if your plan supports it, or paste the runbook address into the chat. A chat assistant that can't make HTTP requests can still read your agent's settings if you paste them, and write the change for you to apply in the Telzino Dashboard.

> [!WARNING]
>
> Don't paste a client secret into a chat assistant that keeps conversation history or shares chats with others. Use a tool that reads secrets from the environment, or give the assistant a short-lived key and delete it afterwards.

## Starter prompt

Copy this into your assistant and fill in the parts in brackets:

```text theme={null}
You are helping me configure Telzino AI agents through the Telzino API.

Before doing anything, read https://docs.telzino.com/configure-with-ai/runbook.md
and follow its ground rules and steps. Use the API reference at
https://docs.telzino.com (or the docs MCP server) and the OpenAPI spec at
https://api.telzino.com/api-doc/openapi. Never guess an endpoint or field.

My API credentials are in the TELZINO_CLIENT_ID and TELZINO_CLIENT_SECRET
environment variables. Never print them or any token.

Work only in organization [organization name or ID].

Rules:
- Read the agent first and show me a before/after table of every field you
  plan to change. Wait for me to say "approved" before you change anything.
- Never delete anything or place calls unless I ask for that exact action.
- After each change, read the agent and its change history to confirm it,
  and tell me the history entry id so I can revert it.

My request: [describe the change]
```

Next, try one of the [example prompts](https://docs.telzino.com/configure-with-ai/example-prompts.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.