Connect a module
Attentive
ShopMCP connects Attentive subscribers, consent, events, catalogs, offers, privacy requests, and webhooks through a native MCP package.
Admin-only launch
1. Create an Attentive private app key
Create a private app API key in Attentive for ShopMCP. Start with read permissions for account checks, subscribers, attributes, catalog, privacy, and webhooks.
Paste the key on Settings - Integrations - Attentive. ShopMCP verifies it with GET /v2/me and falls back to GET /me when needed.
2. What ShopMCP registers
Tools are registered under the attentive_* prefix and combine stable REST endpoints with selected GraphQL beta flows.
- Account checks and GraphQL company verification.
- Subscriber eligibility, batch eligibility, subscribe, and unsubscribe.
- User attributes, bulk jobs, custom attributes, and identity resolution.
- Custom events plus product view, add-to-cart, and purchase events.
- Catalog uploads, coupon codes, privacy requests, and webhooks.
- Seven composite playbooks for lifecycle readiness and audits.
3. Writes and consent
Writes stay off by default. Before enabling them, confirm upstream Attentive scopes and compliance approvals. Subscriber opt-ins require correct sign-up source IDs, legal disclosures, channel-specific SMS/email behavior, and consent evidence.
4. OAuth environment
bashATTENTIVE_CLIENT_ID=... ATTENTIVE_CLIENT_SECRET=... ATTENTIVE_REDIRECT_URI=https://my.shop-mcp.app/api/integrations/attentive/callback ATTENTIVE_DISTRIBUTION_URL=https://... ATTENTIVE_WEBHOOK_SECRET=...
Attentive does not allow dynamic data in the redirect URI, so ShopMCP stores workspace, nonce, and CSRF state in the OAuth state value and validates it during callback.