---
name: adsagent-setup
description: Use when connecting, authorizing, or verifying AdsAgent hosted MCP readiness.
---

# AdsAgent Setup

1. For an installed Claude or Cursor plugin, use its bundled OAuth MCP
   connections. Use the dashboard-generated install prompt only for a manual
   MCP connection in a client without plugin support. Never invent endpoints,
   credentials, local relays, or stdio setup.
2. Reconnect the existing transport and re-list tools after a new connection or
   guide/schema version. Do not re-register or replace a bearer solely for a
   protocol or guide update.
3. Run `setup_get_status` and inspect advertised
   capabilities before any optional workflow.
4. Report channel readiness, blockers, authorization next action, and local
   Skill Pack update notice separately.
5. Never print credentials, infer readiness from screenshots, or change
   customer permissions.

Read [setup-contract.md](setup-contract.md) only when installing, reconnecting,
authorizing a channel, or evaluating a Skill Pack update reminder.

[Data boundary](data-boundary.md) applies.