OpenAI app overview

Clawviyo platform connector for verified merchant inquiries.

Clawviyo exposes one platform MCP endpoint that lets compatible AI clients search listed merchants, inspect merchant profiles, request human verification, submit inquiries, and track inquiry status. The public app surface is the platform endpoint, while merchant-specific endpoints remain scoped fallback surfaces.

Endpoint: https://clawviyo.com/mcpTransport: Streamable HTTP MCPPrimary write gate: verified human email
Core capabilities

What the app does

  • Search Clawviyo merchants by keyword or industry.
  • Describe a merchant’s trust page, enabled tools, and qualification guidance.
  • Request access on behalf of a human by sending a verification magic link.
  • Submit an inquiry to a merchant only after human verification clears.
  • Check long-running task or inquiry status after submission.
Canonical submission surface: The platform app uses /mcp. Merchant-scoped routes such as /c/<slug>/mcp remain available for single-merchant integrations but are not the primary public app listing.
Auth model

Identity, consent, and write actions

Platform grant

OAuth on the platform endpoint establishes a user identity with Clawviyo. It does not grant blanket write permission across all merchants.

Merchant-specific verification

Before a write action such as post_inquiry is accepted for a specific merchant, the user behind the AI assistant still verifies their email through a merchant-facing magic-link flow.

Consent visibility

Consent screens list the requested scopes in plain language and explain that the user’s email remains on file so the merchant can respond to the inquiry.

Reviewer flow

How to validate the app

  1. Connect the Clawviyo platform endpoint in a compatible client.
  2. Run a merchant search and inspect a merchant profile.
  3. Request access using a real human email address.
  4. Complete the verification link sent by email.
  5. Submit an inquiry and then check its status.
Support for review: If you need seeded demo data, reviewer credentials, or sample prompts, use the contact details on the support page.
Limitations

Intentional boundaries

  • The platform connector is for merchant discovery and inquiry workflows, not payments.
  • Write actions are blocked until human verification succeeds.
  • Merchant-specific routes may expose narrower scopes than the platform route.
  • The app is optimized for MCP-capable clients; chat runtimes without a configured connector should use the human-prefill path shown on merchant trust pages.