Other clients

Any MCP client that supports the Streamable HTTP transport can connect to VYG:

https://api.vyg.app/mcp

The server accepts POST requests only; there is no separate SSE endpoint.

Sign in with OAuth

Clients that support MCP authorization discover the sign-in flow on their own: a 401 response points to https://api.vyg.app/.well-known/oauth-protected-resource, which names the authorization server (https://vyg.app). The person signs in, picks a brand and approves the access. See Authentication.

Use an API key

Headless clients, scripts and shared automations can send an API key as a bearer token instead of signing in:

Authorization: Bearer vyg_your_key_here

For example, in Claude Code:

claude mcp add --transport http vyg https://api.vyg.app/mcp \
  --header "Authorization: Bearer vyg_your_key_here"

A key can call the tools permitted by its scopes. Tools marked Sign-in only in the tool catalog require OAuth: campaign changes, discounts, segment changes, Shopify and Klaviyo. See API keys.

Developer tools

Add ?tools=developer to the URL, or send the header x-vyg-mcp-tools: developer, to list the Shopify developer documentation tools as well. See Shopify tools.