Quickstart

Connect an agent to VibeCart in minutes.

VibeCart uses one public Streamable HTTP MCP endpoint. Connect your client to Core for free, or use VibeCart Cloud when you want the managed order/event infrastructure.

Start Cloud — $29/month Full agent guide

Canonical MCP endpoint

https://vibecart.vercel.app/mcp

Generic MCP clients use this endpoint. Keep approval prompts enabled for state-changing commerce tools unless you have deliberately established a trusted policy.

Official MCP Registry

io.github.runjohnray2-lgtm/vibecart

VibeCart is published and verified in the official MCP Registry. The repository automatically republishes and verifies its Registry record when metadata changes.

Connect a client

Use the same backend everywhere.

Claude Code

claude mcp add --transport http vibecart https://vibecart.vercel.app/mcp

VS Code

{
  "servers": {
    "vibecart": {
      "type": "http",
      "url": "https://vibecart.vercel.app/mcp"
    }
  }
}

OpenAI Responses API

{
  "type": "mcp",
  "server_label": "vibecart",
  "server_url": "https://vibecart.vercel.app/mcp",
  "require_approval": "always"
}

Claude, Gemini, Cursor, Codex, ChatGPT, VS Code and other MCP clients all use the shared Core. See the full guide for provider-specific notes and current product UI details.

1 · Connect

Point the agent at `/mcp`.

The agent can inspect products and create trusted one- or multi-item checkout sessions.

2 · Connect your catalog

Keep SKUs and prices in your system.

Set `VIBECART_CATALOG_URL` to a merchant-controlled HTTPS JSON feed. VibeCart reads trusted prices from that source; no TypeScript edit or redeploy is required for normal SKU/price changes.

3 · Go live

Keep your Stripe account.

Configure Stripe secrets server-side. Checkout revenue settles directly to the merchant; VibeCart takes no percentage of merchant sales.

Merchant catalog contract

One HTTPS JSON feed. Same source for agents, carts and checkout.

VIBECART_CATALOG_URL — required for a real remote merchant catalog.

VIBECART_CATALOG_BEARER_TOKEN — optional server-side bearer credential when the feed is private.

VIBECART_MERCHANT_NAME — optional merchant display name used in UCP catalog responses.

The remote source must be public-routable HTTPS. Responses are size-bounded, validated, fetched without redirects, and cached briefly. If a configured remote catalog is unhealthy, VibeCart fails closed instead of falling back to fictional demo products.

{
  "products": [
    {
      "id": "sku-123",
      "name": "Example product",
      "description": "Merchant-controlled product data",
      "priceCents": 4900,
      "image": "https://merchant.example/products/sku-123.jpg",
      "variant": "Optional variant"
    }
  ]
}

Self-host Core

Free

Run the reference implementation yourself, keep your Stripe account, connect the trusted merchant catalog feed, and use MCP/UCP directly.

Open GitHub →

VibeCart Cloud

$29 / month

Managed durable events/orders, fulfillment webhook delivery, retries, monitoring, updates and support around the free Core.

Open Cloud workspace →