Back to Docs
MCP

Vaybel MCP Server

Let any MCP-capable agent drive your Vaybel workspace — generate designs, mockups, and launch-ready assets.

Updated 2026-04-20

What It Is

The Vaybel MCP server lets MCP-capable clients — Claude, ChatGPT, Cursor, or any custom agent — drive your Vaybel workspace directly over the Model Context Protocol. Connect once with a Personal Access Token and your agent can query the catalog, generate designs, render flat mockups, and inspect credits on your behalf.

What It Is

A secure, org-scoped HTTP tool surface for MCP clients. One endpoint, one token, a handful of tools — no SDK, no glue code.

Best For

Agentic workflows: "design and mock up an AOP hoodie for [niche]". The agent picks the blank, writes the prompt, dispatches, polls, and returns a preview — all from chat.

Connection Details

  • Endpoint — https://mcp.vaybel.com/
  • Transport — HTTP + Streamable SSE
  • Auth — Authorization: Bearer <PAT>
  • Token format — vbl_pat_live_... (production) or vbl_pat_test_... (non-production)
  • Protocol version — MCP 2024-11-05

Tools At A Glance

Nine tools cover the full design → mockup loop:

  • Utility — ping
  • Brand DNA — brand_dna.get_brand_dna
  • Catalog — catalog.list_blanks
  • Credits — credits.check_credits
  • Design — design.generate_design, design.get_design_status, design.wait_for_design
  • Mockup — mockup.generate_mockup, mockup.get_mockup_status

Full signatures, return shapes, and credit costs are in the Tool Reference.

What's Next

Get Started

Quickstart walks through creating a token and wiring it into your MCP client in under five minutes.

Before Production

Authentication & Scopes covers PAT lifecycle, scope semantics, and rate limits.