Sign-in
The server uses OAuth 2.1 with PKCE. You sign in once per app:- You add
https://mcp.plivo.com/mcpto your AI app. - The app opens the Plivo login page. Log in as usual, with your password and two-factor authentication.
- Plivo shows Connect an AI app to Plivo, naming the app that is asking. Check the name and click Allow.
- 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.