Claude Code
Give a familiar workflow a new job.
Keep your brand brief alongside your project notes. Connect Vaybel over HTTP MCP, then use the official Vaybel Skills plugin for a guided product-launch workflow.
Set up Claude CodeAlready work in Claude Code, Codex, or an AI research assistant? Bring your clothing brief with you. Connect Vaybel’s product tools, make the assets, and review your next drop in the dashboard.
Your assistant may already hold your audience research, collection notes, and creative direction. Vaybel MCP lets a compatible assistant act on that brief using your workspace’s clothing tools.
Plan in the conversation, create through Vaybel, and open the product to make the visual decisions. You can move between the assistant and dashboard as the collection takes shape.
See what Vaybel MCP can doThe conversation lives in your assistant. The clothing tools and generated assets live in Vaybel.
Give a familiar workflow a new job.
Keep your brand brief alongside your project notes. Connect Vaybel over HTTP MCP, then use the official Vaybel Skills plugin for a guided product-launch workflow.
Set up Claude CodeTurn a project brief into product work.
Connect Vaybel as an HTTP MCP server in Codex. Keep the brief in your project, ask for the next product task, and follow the returned links to review the assets in Vaybel.
Codex connection guideBring research into the brief.
Use your audience research to shape a product direction. Perplexity offers custom remote MCP connectors; check your account’s access and support for Vaybel’s token authentication before connecting.
Check connector requirementsAlready using Cursor? Follow its MCP connection guide. Client availability and authentication options vary; a saved connector is only the first step. Verify access to Vaybel before starting a workflow.
Try a small, specific workflow first. These example prompts give each stage a clear stopping point.
Share the audience, garment, visual direction, and what you want to make. Have your assistant read your Vaybel Brand DNA and check the available blanks.
“Read my Brand DNA. Help me choose a tee blank for a small trail-running collection. Show me three artwork directions before generating anything.”
Choose a direction, create the artwork, and ask for mockups of that product. Open the results in Vaybel to judge the print, placement, and garment.
“Use the second direction on the blank I chose. Create one design, then two mockups. Return the product link so I can review it.”
Carry the chosen product into listing preparation. Check the images, product facts, variants, and destination before you approve publication.
“Prepare an Etsy listing draft for this product using its actual details. Show me the title and description. Leave it unpublished for my review.”
Generation uses Vaybel credits. Ask your assistant to check the balance and confirm the scope of the work before making a batch.
The product brief can be written in plain language. Connecting a coding assistant may involve a settings file or terminal command. If that is not how you like to work, use the Vaybel dashboard directly.
Yes. Cursor supports remote MCP servers and authentication headers. Configure the Vaybel endpoint and token using Cursor’s MCP instructions, then use the same brief, create, and review approach. Vaybel is independent of Cursor.
No. Vaybel uses a hosted HTTP MCP endpoint and a scoped access token. Client settings, environment-variable syntax, available connectors, and account requirements differ. Use the instructions for your assistant and verify the connection before generating assets.
The products and assets created through Vaybel tools belong to your workspace, where you can review and continue the work. Your assistant’s conversation and project files stay in that assistant. Tool access and generation costs follow your Vaybel plan, permissions, and credits.
Create a Vaybel access token, follow your assistant’s setup, and start with one product.