connect

Connect MStack to Meta and Google Ads via authenticated browser sessions.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/akvinayaktiwari/mstack --skill connect-akvinayaktiwari
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect
Source: https://github.com/akvinayaktiwari/mstack/tree/main/connect
Command: npx skills add https://github.com/akvinayaktiwari/mstack --skill connect-akvinayaktiwari

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

This skill solves the friction of manually managing ad account sessions and the security risks associated with sharing credentials, allowing MStack to interact with your ad platforms safely.

Core Features & Use Cases

  • Secure Session Linking: Connects Meta and Google Ads accounts by leveraging your existing browser sessions without ever exposing passwords or 2FA codes.
  • Safety Guardrails: Implements strict spend caps and change percentage limits to ensure no automated action exceeds your risk tolerance.
  • Use Case: A marketer needs to start managing a new Meta Ads account; they use this skill to link the account, set a daily budget ceiling, and enable the MStack safety ledger for all future operations.

Quick Start

Ask the assistant to connect my Meta ad account to get started with MStack.

Frequently Asked Questions about connect

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

FAQPage Schema
How do I securely connect Meta and Google Ads accounts to an automated workflow?

To securely connect Meta and Google Ads accounts, this skill leverages your existing local browser sessions to establish an authenticated connection without exposing passwords or 2FA codes. It directly links your ad platforms to MStack workflows.

How does browser session authentication work for ad account linking?

Browser session authentication works by utilizing your active local browser profile to authorize external ad platforms. This mechanism prevents credential sharing risks by maintaining session management directly through your existing authenticated browser environment.

Can I enforce spend caps and budget limits when linking ad accounts?

Yes, you can enforce spend caps and budget limits. The skill mandates user-defined budget parameters and strict spend-cap configurations during initialization to ensure all automated account operations remain within your risk tolerance.

Do I need local browser access to initialize ad platform connections?

Yes, local browser access is required to initialize the operational environment. The session management process depends on your local browser profile integration to safely authenticate external advertising platforms like Meta and Google Ads.

What happens if I do not set a daily budget ceiling for my Google Ads account?

Mandatory spend-cap configurations are enforced during initialization, meaning the operational environment requires user-defined budget parameters. Without setting a daily budget ceiling, the safety guardrails cannot be activated for automated ad account operations.

Is jq required to manage ad account sessions and spend caps in MStack?

Yes, jq is a required dependency. This command-line JSON processor is necessary for the skill to function properly when establishing secure connections and enforcing mandatory spend-cap configurations for your advertising accounts.