Virtneu Auth Docs

Management MCP

Connect an OAuth-capable AI client to one Studio app and environment.

The server supports MCP protocol 2026-07-28 and stateless compatibility with 2025 protocols, including 2025-06-18. Legacy clients use the standard initialize handshake over Streamable HTTP; no MCP protocol session, standalone SSE transport, or resumability is provided. OAuth grants remain independently managed. Add it to a client that supports OAuth and Streamable HTTP:

https://auth-api.virtneu.com/mcp
  1. Sign in to Studio from the OAuth prompt.
  2. Choose an existing app, environment, and permissions for the connection. Create and enable your app in Studio before connecting.
  3. Review and approve access. Manage and revoke the connection in Studio → AI connections.

Configure an SDK project

With config:read, call get_integration_config to get the installation command, API base URL, app ID, environment, and SDK environment variable names. Use get_credential_status to list key metadata or look up a specific key by ID. Store the key used by your backend as VAUTH_SERVICE_CREDENTIAL.

Check and configure authentication email

Backend mail diagnostics are available in SDK 0.4.0 and later; install the SDK from npm.

get_integration_config and check_integration report mail readiness separately from routing and API-key readiness. With config:read, call get_mail_readiness for the selected App/environment. The result contains configured, tested, enabled, service_configured, ready, blockers and a direct settings_url; it never returns or decrypts the provider key. An unavailable route reports no mail evidence, rather than claiming email is ready.

A successful provider test records provider acceptance, not inbox delivery. A ready configuration does not prove a real login. Validate registration, sign-in, session renewal and logout with an actual controlled mailbox; validating an invalid session token is not a login acceptance test.

Workspace owners, admins, and developers can grant config:write for a test connection and use this sequence:

  1. Read get_mail_readiness and its revision. Prefer entering provider credentials directly in Studio at settings_url. Alternatively, use save_mail_configuration only when explicitly authorized and supply secrets directly from a protected source, keeping them out of chat/logs. A new draft disables sending and clears earlier test evidence. Omit api_key to keep an unchanged provider/account's key.
  2. Call test_mail_configuration with that revision, a controlled recipient and a stable UUID operation_id. Retry a timeout with identical input and the same ID; changing recipients requires a new ID. Do not blindly retry an ambiguous Cloudflare delivery result.
  3. Confirm actual receipt with the developer, then call set_mail_enabled with enabled: true and the tested revision. An untested draft cannot be enabled.
  4. Re-read readiness. Test and production have separate configuration and keys. MCP mail mutations reject production. A stale revision returns MAIL_CONFIGURATION_CONFLICT; reread before deciding on a new change.

Backend integrations can call GET /v1/integration/mail-readiness (SDK getMailReadiness()) with their selected App/environment service credential and auth:challenge scope. This endpoint is read-only and does not send email. A MAIL_SERVICE_NOT_CONFIGURED blocker is a platform mail-service issue; an unconfigured, untested or disabled App sender is configured in Studio.

Create a test API key

Workspace owners and admins can explicitly grant credentials:write when connecting to a test environment. Reauthorize existing connections to add this permission.

Call create_credential with the authorized app and environment, a key name, the required service scopes, and a UUID operation_id. The key is returned once. Save it directly in your backend secret manager and keep it out of chat and logs. If a response is lost, query key metadata and manage the existing key in Studio. Replaying the same operation ID does not reveal the secret.

What the tools can do

TaskTools
Inspect the selected applist_applications, get_application
Check integration and credentialsget_integration_config, check_integration, get_credential_status, get_service_status
Inspect email preparationget_mail_readiness
Configure test emailsave_mail_configuration, test_mail_configuration, set_mail_enabled
Create a test API keycreate_credential
Inspect activityget_usage, list_authentication_events, list_application_audit, list_configuration_events
Inspect users and sessionslist_users, get_user, list_user_sessions
Manage test securityupdate_authentication_policy, disable_user, enable_user, revoke_user_sessions
Submit product feedbacksubmit_feedback

Tool availability depends on the approved scopes and your current workspace role. App data writes are limited to test. Use the SDK or HTTP API for end-user registration, login, and session validation.

On this page