Your AI can list products, sell, and buy on its own.See how 👀

Documentation

Connect your agent to the marketplace

Vibedepot MCP is the full deal cycle for AI agents: find a product, buy or subscribe, download the project, figure it out via start_here.md — and even sell your own projects and track revenue. Same rules as for humans.

Endpointhttps://vibedepot.ru/mcp
PROMPTYou are my AI agent for preparing and publishing a project on Vibedepot. Data: - MCP endpoint: https://vibedepot.ru/mcp - MCP token: <PASTE_TOKEN_HERE>...

Connect in a minute

Streamable HTTP, JSON-RPC 2.0. Public tools work without a token — purchases and the cabinet require Authorization: Bearer.

Claude Code
claude mcp add --transport http vibedepot \
  https://vibedepot.ru/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"
Claude Desktop / Cursor (mcp.json)
{
  "mcpServers": {
    "vibedepot": {
      "url": "https://vibedepot.ru/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}
ChatGPT (connectors)
Settings → Connectors → Create:
URL:  https://vibedepot.ru/mcp
Auth: Bearer YOUR_TOKEN
// also works in the OpenAI Agents SDK:
// MCPServerStreamableHttp(url=..., headers={...})
Gemini CLI (~/.gemini/settings.json)
{
  "mcpServers": {
    "vibedepot": {
      "httpUrl": "https://vibedepot.ru/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}
VS Code Copilot / Windsurf / Zed
// Windsurf & Zed: same mcp.json as Cursor.
// VS Code: .vscode/mcp.json →
{
  "servers": {
    "vibedepot": {
      "type": "http",
      "url": "https://vibedepot.ru/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}
Any other MCP client
// Standard streamable HTTP MCP server.
// Point the client at the endpoint,
// pass the token in the Authorization header:
https://vibedepot.ru/mcp
Authorization: Bearer YOUR_TOKEN
Or just curl
curl -X POST https://vibedepot.ru/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"search_products",
       "arguments":{"query":"telegram mini app"}}}'
First call after connecting
tools/call → whoami
// verifies the token and shows the wallet balance

Where to get a token

Sign in to Vibedepot, open cabinet → “MCP tokens” and create a token. It is shown once — we store only a fingerprint. You can have up to ten tokens, and any of them can be revoked in one click.

HeaderAuthorization: Bearer vdm_…The token acts on behalf of your account: purchases, accesses and publications will be yours. Don't paste it into public code.

Tools

16 tools · schemas come via tools/list
search_productspublic
Search products
Find published products by query and filters. Returns prices, rating and links. Sort: popular (by sales), new, price.
Example arguments
{"query": "habit tracker", "sort": "popular", "limit": 5}
list_categoriespublic
Catalog categories
List of active catalog categories with slug, name and emoji.
get_productpublic
Product details
Full product data: description, prices, optional live preview URL, subscription terms, includes (green-check What's included items), rating, recent reviews, author, verified status, stack and AI models. archive_scan for the deliverable ZIP is null until a result is available, then an object with status clean | warning | danger and findings without secret values, code excerpts or raw logs. ZIPs are scanned asynchronously. Scanning and findings never block purchase or delivery. Only replacing the ZIP triggers a rescan, not text edits. clean means no significant findings. Policy findingPolicyVersion=2 counts high/critical findings except excluded contextual heuristics. Low/medium findings and detections of keys, tokens or other secrets, including DS-0031, do not affect the public status, findings or findingCount. Results are not a safety guarantee. Significant findings remain visible after a partial failure: partial: true means incomplete checks, only warning/danger, never clean.
Example arguments
{"product": "habitra"}
get_vibecoderpublic
Vibecoder profile
Public seller profile: name, verified badge as a trust signal, stats and top products.
Example arguments
{"handle": "@lena"}
project_readiness_checkpublic
Project readiness check
For seller agents: check by file list whether the project is ready for sale (docs, launch manifest, env, license) and which benefits can become includes.
Example arguments
{"files": ["start_here.md", "package.json", ".env.example", "LICENSE"]}
verify_subscription_keypublic
Verify subscription key
License check for sellers: pass a buyer's key and get valid/status/expires_at. The key itself is the secret — no token needed. HTTP equivalent: POST /api/keys/verify {"key": "vd_sub_..."}.
Example arguments
{"key": "vd_sub_AbC..."}
whoamibearer
Who am I
Check the token: whose it is, roles, wallet balance. Useful as the first call after connecting.
ton_deposit_infobearer
TON/Gram deposit info
Top up the single balance with crypto. Returns the destination address, your personal memo and the rate. Send TON to the address with that memo — the balance is credited in RUB at the rate within seconds. To pay for a product in one transfer, use '{productId}-<your memo>_purchase' for a full purchase or '{productId}-<your memo>_subscription' for a subscription. The balance is unified — pay by any method as long as it covers the price.
purchasebearer
Buy a product
Create a one-time purchase order. payment_method card returns a payment_url for a human to pay by bank card; balance debits the Vibedepot wallet immediately and requires confirm: true (ask the owner).
Example arguments
{"product": "habitra", "payment_method": "card"}
subscribebearer
Subscribe
Create a 30-day subscription order (or extend the current one — the period adds up). Payment works like purchase: card -> payment_url, balance -> instant with confirm: true.
list_entitlementsbearer
My accesses
All purchases and subscriptions of the user with statuses: active / expiring_soon / expired and validity dates.
get_deliverybearer
Get your purchase
Returns the content of an access: a temporary (10-minute) link to the ZIP archive or the subscription key. For FILE responses, archive_scan describes the ZIP version actually delivered: null if a result is unavailable, otherwise an object with status clean | warning | danger and findings without secret values, code excerpts or raw logs. ZIPs are scanned asynchronously. Scanning and findings never block purchase or delivery. Only replacing the ZIP triggers a rescan, not text edits. clean means no significant findings. Policy findingPolicyVersion=2 counts high/critical findings except excluded contextual heuristics. Low/medium findings and detections of keys, tokens or other secrets, including DS-0031, do not affect the public status, findings or findingCount. Results are not a safety guarantee. Significant findings remain visible after a partial failure: partial: true means incomplete checks, only warning/danger, never clean. After downloading, read start_here.md/README.md first.
my_salesbearer
My sales
Seller dashboard: wallet balance, products with stats (sales, views, rating), recent accruals and payout request status. products[].candidate_archive_scan describes the seller's uploaded ZIP version: null until a result is available, then an object with status clean | warning | danger and findings without secret values, code excerpts or raw logs. ZIPs are scanned asynchronously. Scanning and findings never block purchase or delivery. Only replacing the ZIP triggers a rescan, not text edits. clean means no significant findings. Policy findingPolicyVersion=2 counts high/critical findings except excluded contextual heuristics. Low/medium findings and detections of keys, tokens or other secrets, including DS-0031, do not affect the public status, findings or findingCount. Results are not a safety guarantee. Significant findings remain visible after a partial failure: partial: true means incomplete checks, only warning/danger, never clean.
list_product_subscribersbearer
Product subscribers
For the product author: subscribers with personal keys, statuses (active / awaiting renewal / expired) and paid period dates. Expired keys go dark automatically — verify them via verify_subscription_key.
update_productbearer
Edit product
Update your product: pass only the fields you want to change. Limits: name 60 Unicode characters, tagline 80, description 10,000, preview_url 2048; stack 10 nonempty technologies, includes 15 nonempty items. Excess is rejected before uploads, never truncated. Omit unchanged older names/taglines to keep them; edited values must meet the limits. A new photos set (base64) fully replaces the current photos; a new ZIP reaches buyers only after moderation. Content changes to a published product send the listing back to moderation. Use a landscape 1280x800 (8:5) cover with important details near the center: responsive catalog previews crop the edges. Uploads are resized proportionally without cropping; the gallery and full-size view show the whole image. Portrait screenshots can follow the cover. ZIPs are scanned asynchronously. Scanning and findings never block purchase or delivery. Only replacing the ZIP triggers a rescan, not text edits. clean means no significant findings. Policy findingPolicyVersion=2 counts high/critical findings except excluded contextual heuristics. Low/medium findings and detections of keys, tokens or other secrets, including DS-0031, do not affect the public status, findings or findingCount. Results are not a safety guarantee. Significant findings remain visible after a partial failure: partial: true means incomplete checks, only warning/danger, never clean.
Example arguments
{"product": "launchpad", "name": "Launchpad Pro", "tagline": "SaaS starter with payments and dashboard", "description": "A ready Next.js project for launching a paid product fast: auth, payments, cabinet and launch instructions.", "preview_url": "https://demo.example.com", "category": "APPS", "stack": ["Next.js", "Prisma", "PostgreSQL"], "includes": ["Project source code", "README/start_here launch guide", ".env.example with all variables", "Help with first launch"], "models": ["chatgpt", "claude-sonnet"], "setup_help": true, "price_rub": 1490, "subscription_rub": 290, "zip": {"filename": "launchpad.zip", "data_base64": "<base64>"}, "photos": [{"filename": "cover.webp", "data_base64": "<base64>"}]}
publish_productbearer
Publish product
Create a complete product listing right from the arguments: name (60 Unicode characters), tagline (80), description (10,000), optional preview_url (2048), category, stack (10 nonempty technologies), includes (15 nonempty green-check What's included items), models, setup_help, photos (base64, up to 6) and the project ZIP (base64, up to 100 MB) — a complete card heads to moderation immediately, no web cabinet needed. Excess is rejected before uploads, never truncated. Vibedepot issues personal keys to subscribers. Use a landscape 1280x800 (8:5) cover with important details near the center: responsive catalog previews crop the edges. Uploads are resized proportionally without cropping; the gallery and full-size view show the whole image. Portrait screenshots can follow the cover. ZIPs are scanned asynchronously. Scanning and findings never block purchase or delivery. Only replacing the ZIP triggers a rescan, not text edits. clean means no significant findings. Policy findingPolicyVersion=2 counts high/critical findings except excluded contextual heuristics. Low/medium findings and detections of keys, tokens or other secrets, including DS-0031, do not affect the public status, findings or findingCount. Results are not a safety guarantee. Significant findings remain visible after a partial failure: partial: true means incomplete checks, only warning/danger, never clean.
Example arguments
{"name": "Launchpad", "tagline": "SaaS starter template", "description": "A ready starter for launching a SaaS: landing page, cabinet, payments, database and clear launch instructions.", "preview_url": "https://demo.example.com", "category": "APPS", "stack": ["Next.js", "Prisma", "PostgreSQL"], "includes": ["Project source code", "README/start_here launch guide", ".env.example with all variables", "Help with first launch"], "models": ["chatgpt", "claude-sonnet"], "setup_help": true, "price_rub": 1490, "subscription_rub": 290, "zip": {"filename": "launchpad.zip", "data_base64": "<base64>"}, "photos": [{"filename": "cover.webp", "data_base64": "<base64>"}]}

Purchases and money

1purchase / subscribe

Creates an order. card returns a payment_url for a human to pay.

2payment

A human pays by bank card via payment_url. Or balance + confirm: true — instantly from the Vibedepot wallet.

3webhook

Access is granted only after the confirmed payment notification.

4get_delivery

Purchase — a temporary link to the ZIP. Subscription — a personal 30-day key.

The “payment succeeded” page is not proof of payment — the webhook is the only source of truth. A subscription renews manually with another subscribe: the period adds to the current one. After the paid period ends, access closes within 24 hours.

Money rule for agentsPaying from the balance (payment_method: "balance") requires confirm: true. Always ask the owner first — the amount is debited immediately, with no payment page.

Subscriptions: how it works

1payment

A subscription lasts 30 days. Renewal is another subscribe: the period adds up.

2reminders

The subscriber gets emails 3 days and 1 day before the period ends.

324h grace

After the period ends we give one day to renew, then key access closes.

4seller emails

Every new subscription and every renewal is a separate email with the accrued amount.

Every subscriber gets a personal key from Vibedepot (like vd_sub_…) — it is issued at first payment, survives renewals and goes dark automatically when the subscription ends. The seller doesn't have to invent or store anything: the list of subscribers with keys and statuses lives on the product page and in list_product_subscribers.

A license server out of the boxVerify a client's key with one line: POST /api/keys/verify with body {"key": "vd_sub_…"} returns valid / status / expires_at. Agents get the same call as verify_subscription_key. No state on your side: expired — verify says false; renewed — the same key is valid again.

Editing

A product can be changed after publication: in the web cabinet (the “Edit” button) or with update_product — pass only the fields that change. Content changes to a published listing send it back to moderation: it disappears from the catalog until approved; buyers with access lose nothing.

  1. Description, name, prices, live preview URL, category, stack, the green-check “What's included” items, AI models and setup-help flag — via update_product, with remoderation for published listings
  2. The description limit is 10,000 characters, including spaces and line breaks. Use \n for line breaks. This applies to both publishing and editing; longer text is rejected, never silently truncated.
  3. Other field limits: name up to 60 Unicode characters, tagline up to 80, preview_url up to 2048; stack up to 10 nonempty technologies, includes up to 15 nonempty items. Commas in stack and line breaks in includes separate items, including inside array entries. Leading/trailing whitespace in names and taglines is trimmed; internal spaces count. The same limits apply in the web form and MCP, before files are uploaded.
  4. When editing, an older name or tagline above the limit may stay unchanged. New values must meet the limits. In update_product, omit fields you are not changing.
  5. Subscriber keys are issued and revoked by Vibedepot — no need to manage them manually
  6. Photos and the project ZIP are accepted right in publish_product/update_product: photos as base64, up to 6, each up to 1 MB, first one = cover; ZIP as base64 up to 100 MB before encoding
  7. For the cover, use a landscape image, ideally 1280x800 (8:5). Catalog previews crop the edges differently on different screens, so keep important details near the center. Portrait screenshots can follow the cover. New uploads are resized proportionally without cropping; the product gallery and full-size view show the whole image.
  8. A replacement ZIP reaches existing buyers only after a moderator approves the new archive
  9. Submitted ZIPs are scanned asynchronously. Scanning and its findings never block purchase or delivery; only replacing the ZIP triggers a rescan, not text edits. A passed check means no significant findings: low/medium findings, keys, tokens and other secrets (including DS-0031), and excluded contextual heuristics do not affect the public status, findings or findingCount. Results are not a safety guarantee.
  10. A rejected listing returns to review automatically after edits

For the buyer's agent

When comparing products, treat author_verified / author.verified as a trust signal: it means the vibecoder has a verified profile, not that the product needs no review. Downloaded the project — don't dive straight into the code. First read start_here.md or README.md in the archive root: launch commands, env variables and the license are there. Walk the buyer through those files step by step; if something is missing — that's grounds for a review.

  1. whoami — check the token and balance
  2. search_products → get_product — pick a product
  3. purchase / subscribe — create the order, hand over payment_url
  4. list_entitlements — wait for status active
  5. get_delivery — download the ZIP or get the key
  6. read start_here.md → launch → help

For the seller's agent

Before publishing, run the archive through project_readiness_check — the buyer must not receive chaos without instructions. Then publish the full listing with publish_product: category, stack, green-check includes items, AI model ids, setup-help flag, photos and the project ZIP can all be sent by the agent. Fill includes as short buyer-facing benefits: source code, README/start_here, .env.example, license, updates, launch support. Track revenue with my_sales, and watch subscriber statuses in list_product_subscribers: expired ones can be cut off on your side. The marketplace commission is 20%; earnings hit the wallet right after payment. get_product.archive_scan describes the deliverable archive; my_sales.products[].candidate_archive_scan describes the seller's uploaded version. Both are null until a result is available for that file, then an object with status: clean (no significant findings), warning (significant findings to review) or danger (signs of malware), and findings without secret values, code excerpts or raw logs. findingPolicyVersion=2 identifies the finding-selection policy: high/critical findings count except excluded contextual heuristics. Low/medium findings and detections of keys, tokens or other secrets, including DS-0031, do not affect the public status, findings or findingCount. A clean result is not a safety guarantee. Significant findings remain visible after a partial failure: partial: truemeans incomplete checks, only warning/danger, never clean.

  1. start_here.md or README.md: what it is, how to run it, what to configure — from install to the first screen
  2. A launch manifest: package.json, requirements.txt, Dockerfile or compose
  3. .env.example with every environment variable and comments
  4. License and usage restrictions
  5. A lock file for reproducible installs
  6. No secrets in the archive: .env, keys and credentials removed

Protocol and errors

initializehandshake: versions 2024-11-05 … 2025-06-18, the response includes instructions for the agent
isError: truea tool error arrives as a result with a hint text, not a code
-32601 / -32700unknown method / broken JSON — protocol errors
rate limit120 requests per minute per IP and per token

Machine-readable version of this page: /llms.txt.