VELYGA MCP AUTHORIZATION

Connect to AI.
On your terms.

A first-party Velyga authorization experience is being prepared. Your AI can ask to connect, but only you and your device can grant the appropriate permissions.

Authorization migration in progress

This is not a live authorization page yet

Velyga Google sign-in is verified on this website. MCP still uses GitHub owner bootstrap while its signed, single-use approval bridge is tested. This page does not grant access tokens.

Velyga Google sign-in works. The MCP approval bridge is in testing.
HOW MCP AUTHORIZATION WILL WORK

Your Velyga Account

Google identity + your consent

Velyga MCP authorization

OAuth / PKCE and token issuance

Your Android device

Existing pairing + local permission checks

THE SECURITY BOUNDARY

Logging in is not permission to control your phone.

A Google session will prove who is signed in. The Velyga MCP server must separately validate the requested client, exact redirect URI, state, PKCE challenge, authorization scope, and device authority before it grants anything. The local Android Master OFF always wins.

Identity
OAuth authorization
Device consent

No account sign-in, authorization code, or access token is issued from this page.

Already have a Velyga MCP connection?

Your existing authorized setup remains unchanged during this transition. Do not remove it to try this new page.

Read connection guide
Velyga MCP Authorization | Velyga