MCP Quickstart

Open Dashboard → Settings → MCP. Click Create token, give it a label, and pick scopes. All current public scopes are selected by default so the MCP server and Vaybel Skills work immediately. Uncheck scopes only when you are intentionally limiting a token.

Store the token once in Claude Code settings:

{
  "env": {
    "VAYBEL_PAT": "vbl_pat_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  }
}

Then add the Vaybel MCP server using that environment variable:

claude mcp add-json vaybel '{"type":"http","url":"https://mcp.vaybel.com/","headers":{"Authorization":"Bearer ${VAYBEL_PAT}"}}' --scope user

Install the official Vaybel Skills plugin:

/plugin marketplace add vaybel/skills
/plugin install vaybel@vaybel

Restart Claude Code after changing settings or plugin state.

Every MCP-capable client uses the same server shape. For clients with a local config file, keep the raw token out of the file and reference VAYBEL_PAT:

{
  "mcpServers": {
    "vaybel": {
      "type": "http",
      "url": "https://mcp.vaybel.com/",
      "headers": {
        "Authorization": "Bearer ${VAYBEL_PAT}"
      }
    }
  }
}

Config locations for the common clients:

• Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json
• Claude Code — use claude mcp add-json or project/user .mcp.json
• Gemini CLI — add to ~/.gemini/settings.json
• ChatGPT — add as a custom connector from Settings → Connectors (paste the URL and Bearer header in the UI; no local file)

Restart the client after saving if it loads MCP server configs on startup.

Ask your agent to call the ping tool, or send the JSON-RPC frame directly:

curl -N -X POST https://mcp.vaybel.com/ \
  -H "Authorization: Bearer $VAYBEL_PAT" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ping","arguments":{"echo":"hello"}}}'

A successful response carries structuredContent.echo = "hello". A 401 means the Authorization header didn't land — re-check your client config and restart. Any other error shape: head to Tool Reference to match against the expected return.

From Claude Code with Vaybel Skills installed, run:

/vaybel:launch-product "washed archive tee graphic"

Or from any MCP client, ask the agent something concrete:

Find the top trend in my brand's niche this week. Pick a hoodie blank, design three concepts on it, render Pro mockups, and create a draft listing for TikTok Shop.

The agent picks tools from the full surface — trend.list_trends, catalog.list_blanks, design.generate_design, mockup.generate_mockup, listing.create_listing — and chains them automatically. Add content.generate to produce a video, slideshow, carousel, or single-photo post (then social_post.generate + social_post.publish to fan out to TikTok / Instagram / YouTube / X), or optimize.optimize_product to import a Printify product you already have. The Tool Reference groups every tool by workflow.