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

# Sign-in and security

> How the Plivo MCP server signs you in, what its token can reach, and how your credentials stay protected.

## Sign-in

The server uses OAuth 2.1 with PKCE. You sign in once per app:

1. You add `https://mcp.plivo.com/mcp` to your AI app.
2. The app opens the Plivo login page. Log in as usual, with your password and two-factor authentication.
3. Plivo shows **Connect an AI app to Plivo**, naming the app that is asking. Check the name and click **Allow**.
4. The app receives a token that expires in 30 days. When it expires, the app asks you to sign in again.

## What is protected

* **Your Auth Token never leaves Plivo.** The app holds only a limited token. The MCP server stores no credentials.
* **The token reaches only what the MCP needs.** It covers 135 operations across messaging, voice, numbers, SIP trunking, AI agents, Audio Streaming, number masking, Verify and account details.
* **Sub-accounts are left out.** Plivo's sub-account API returns the sub-account's Auth Token, which would outlive the MCP token, so those operations aren't available.
* **The consent screen names the real app.** Plivo names the app by the address it returns to, so an app can't pass itself off as another.
* **Sign-in codes are single use** and expire in 60 seconds.
* **No secrets in the chat.** Passwords, tokens and other secret fields are hidden at any depth in replies and approval previews.

## Revoke access

The token shows in the console as **Plivo MCP**. Revoke it to disconnect the app straight away.
