MCP Quickstart

Open Dashboard → Settings → API & 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.

Vaybel uses the hosted HTTP endpoint https://mcp.vaybel.com/ with a Personal Access Token in the Authorization: Bearer header. Each assistant has its own configuration format; a config copied from another client may not work.

Codex: add the server to your Codex MCP configuration. Make VAYBEL_PAT available in the environment that starts Codex:

[mcp_servers.vaybel]
url = "https://mcp.vaybel.com/"
bearer_token_env_var = "VAYBEL_PAT"

Follow the Codex MCP guide for the configuration location and setup options for your Codex client.

Cursor: use its remote MCP configuration and environment-variable syntax:

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

See Cursor’s MCP guide for project and global settings. Make the environment variable available to Cursor before connecting.

Perplexity: check your account’s custom remote connector options. Select Streamable HTTP and verify that its authentication settings can send your Vaybel token as a Bearer header. Connector availability depends on the account and organization settings. This Vaybel connection has not yet been verified end to end in Perplexity.

For other assistants, check remote HTTP and Bearer-token support in the client’s own instructions. Restart clients that load their configuration at startup, then verify the connection in the next step.

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". The dual Accept header is required — sending only application/json returns 406. 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, catalog.list_blanks, design.generate, mockup.generate, integration.list, listing.create — and chains them automatically. Generation tools return a handle; the agent polls <domain>.get_generation(handle, wait_sec) until done (waits cap at 50s per call). 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.import_product to import a Printify product you already have. The Tool Reference groups every tool by workflow.