Zylvie

@zylvie fetch my user profile and show me what account permissions I currently have

Retrieved authenticated user profile for account ID zyl_acc_8x3k9m. Your account is on the Business tier with admin-level permissions. Active features include product management, webhook configuration, and API access. Account created March 2024, last login 2 hours ago. Current API rate limit: 1,000 requests/hour, 847 remaining in this window.

This example uses the Get Authenticating User tool to verify account state before performing other operations. Useful for confirming API key validity and understanding what actions your token permits. Requires a valid API key with read:user scope.

@zylvie create a new product called "Premium Support Package" with three tiers: Basic at $49/mo, Pro at $99/mo, and Enterprise at custom pricing

Created product "Premium Support Package" (ID: prod_7h2n4k) with three pricing tiers. Basic tier configured at $49/month with standard support hours. Pro tier set to $99/month with priority response SLA. Enterprise tier marked as custom pricing requiring sales contact. Product is now live in your Zylvie catalog and available for customer selection. Webhook notifications sent to your configured endpoints.

Demonstrates the Create Product tool's ability to handle complex product structures with multiple pricing options. This action immediately makes the product visible in your storefront—test in a sandbox environment first if you're unsure about configuration. Side-effect: triggers any active product.created webhooks.

@zylvie list all my active webhooks, then unsubscribe the one pointing to the old staging URL https://staging-old.example.com/hooks

Found 4 active webhooks in your account. Located webhook workflow_9x4m2p subscribed to https://staging-old.example.com/hooks (events: product.created, order.completed). Successfully unsubscribed and deleted this workflow. Remaining active webhooks: 3 endpoints monitoring production events. The staging URL will no longer receive notifications from Zylvie.

Shows the Unsubscribe Webhook tool cleaning up outdated integrations. The AI first identifies the target webhook by URL, then removes it—this is a destructive action with no undo. Useful for webhook hygiene but verify the URL carefully before confirming deletion.

When Zylvie makes sense for product data workflows

A 3-person Shopify brand managing 40 SKUs with complex variant logic (size, color, custom engraving) uses Zylvie to push new products from their internal planning sheet into their storefront. The Create Product tool handles the nested custom options that break in simpler integrations. This works if your catalog updates happen in batches (weekly drops, seasonal launches) rather than real-time. If you're syncing hundreds of products daily or need bidirectional inventory updates, Zylvie's 3-tool scope won't cover it—you'd want a full e-commerce MCP. For small-batch brands launching 5-15 products a week, the API key setup and custom-option support justify the integration.

Zylvie's webhook tool solves a narrow dev-ops problem

A 2-engineer team building a Zylvie integration for a client spins up test webhooks during QA, then needs to tear them down before production. The Unsubscribe Webhook tool lets them script the cleanup instead of clicking through the vendor UI. This is a one-time or low-frequency task—useful during the build phase, irrelevant once the integration is live. If your team isn't actively developing on Zylvie's platform, you'll never touch this tool. For agencies or dev shops maintaining multiple Zylvie clients, it saves 10 minutes per project. For end-user teams just using Zylvie's storefront, skip this MCP entirely.

When Get Authenticating User fits a compliance step

A 5-person customer success team handling refund requests uses the Get Authenticating User tool to verify which Zylvie account is tied to the support ticket before processing changes. This matters if your team shares API keys across multiple storefronts or white-label instances—you need to confirm you're acting on the right account. The tool returns profile data, not transaction history, so it's a gate-check, not a full lookup. If your team only manages one Zylvie account or already has user context from your ticketing system, this adds no value. For multi-tenant support desks or agencies juggling client accounts, it prevents costly mistakes.