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

# Connect your AI

> Connect your AI · DoglyTdc Scripts

Chat apps use OAuth in their own connector settings. Add the MCP address, choose OAuth, sign in to DoglyTdc, review the client, account, callback and access, then authorize. Never paste passwords, API keys or tokens into chat.

```text theme={null}
https://ucsyxzpdbnuyehizezvb.supabase.co/functions/v1/doglytdc-scripts-api/scripts/mcp
```

Agents running on your own computer use the installer. A command executed in an isolated chat terminal does not configure that chat app’s connector.

[CLI](https://docs.doglytdc.dev/en/scripts/mcp/install-with-command.md)

| Scope | Access |
| - | - |
| `scripts.read` | Read |
| `scripts.write` | Create / edit |
| `scripts.publish` | Release / rollback |
| `functions.deploy` | Backend deployment |
| `users.manage` | User access management |
| `ai` | Account AI usage |

After the initial login consent, tool confirmation belongs to the AI client. There is no additional per-action approval queue in the DoglyTdc dashboard. Ownership, scopes, revocation and explicit deny rules still apply.


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