mx-auth-login

Name: mx-auth-login
Availability: InStock
Author: MixShift

Authenticate users against the MixShift warehouse with token-based access.

2|Updated May 13, 2026

Search Tags:#authentication #token-based #secure access #MixShift #service credential

Ready to run

npx skills add https://github.com/miXshift/mx-claude-plugin --skill mx-auth-login

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mx-auth-login
Source: https://github.com/miXshift/mx-claude-plugin/tree/main/plugins/mixshift-ai/skills/mx-auth-login
Command: npx skills add https://github.com/miXshift/mx-claude-plugin --skill mx-auth-login

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the authentication process against the MixShift warehouse, allowing users to securely sign in and access their data without manual intervention.

Core Features & Use Cases

Interactive Sign-In: Offers a simple, user-friendly sign-in experience for human users, utilizing device-code orchestration and PKCE browser flow.
Service Credential Setup: Provides an automated way to set up service credentials for unattended runs, such as scheduled tasks and CI pipelines.
Token-Based Flow: Ensures that credentials are stored securely and never expose raw MySQL passwords or IP whitelisting.
Session Attribution: Collects self-attested work emails for interactive sign-ins, providing session attribution on the interactive paths.

Quick Start

Run 'mx-auth-login' to start the authentication process and follow the on-screen instructions.

Frequently Asked Questions about mx-auth-login

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I authenticate to a MixShift warehouse for automated CI pipelines?▼

To authenticate to a MixShift warehouse for automated pipelines, you can set up service credentials for unattended runs. This token-based flow securely stores credentials without exposing raw passwords, enabling scheduled tasks.

What is the best way to handle secure token-based access for MixShift data gateways?▼

Secure token-based access for MixShift data gateways is handled through interactive sign-ins or service credential setup. It uses device-code orchestration and PKCE browser flow to ensure credentials are stored safely.

Does MixShift authentication require IP whitelisting to access the warehouse?▼

MixShift authentication does not require IP whitelisting or raw MySQL passwords. The token-based flow securely manages access through the data gateway, eliminating the need for manual network configurations.

How do I start an interactive sign-in for MixShift warehouse access?▼

To start an interactive sign-in for MixShift warehouse access, run the authentication command and follow the on-screen instructions. This utilizes a PKCE browser flow and collects self-attested work emails for session attribution.

Why do I need the mx-legacy-auth service for MixShift secure access?▼

The mx-legacy-auth service is required because the MixShift secure access process operates within the constraints of the MixShift data gateway. It provides the necessary backend support for both interactive and service credential authentication.

Can I use service credentials for unattended runs without exposing database passwords?▼

You can use service credentials for unattended runs without exposing database passwords. The token-based authentication mechanism ensures raw MySQL passwords are never exposed during scheduled tasks or CI pipeline executions.