Xbitto MCP gives an AI agent a creator-account toolbox for links, paywalls, content uploads, and orders.
Inspect the account, credit balance, and payout wallets.
Create, list, search, and get short links; set up/update paywalls with pricing, title, description, cover, access codes, payer verification, device limits, and payout wallets.
Manage paywall code pools: add license keys/accounts/links from text or files, and check remaining vs delivered.
Sell galleries of 1–20 images, videos with optional preview clips, and multi-episode series with free episodes; add episodes to existing series.
Track background upload jobs and list/get Vault content status.
List/get orders and confirm or reject payments on hold only when the creator instructs it.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Xbitto MCP Create a 9 USDT paywall link to example.com/course and add keys.txt to its pool."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that lets an AI agent (Claude, Cursor, or any MCP client) work in your Xbitto creator account: create short links and paywall links, sell accounts, license keys and other codes by the hundred, and upload galleries, videos and whole dramas (short series in episodes) from your computer.
It runs on your own computer. Files go straight from your computer to your own Bunny account, using upload addresses the Xbitto API signs. They never pass through Xbitto.
Full docs: xbitto.com/docs.
Node.js 20 or newer
An Xbitto account with a verified email and at least one payout wallet
An API key: in the Xbitto dashboard, open AI Agents and select Create Key. Copy it right away; it is shown once.
For Content: Bunny Stream (videos, dramas) and/or Bunny Storage (galleries) connected in Settings
Related MCP server: Longwave
There is no npm package yet; the server installs straight from this repository.
The dashboard's AI Agents page shows these steps with your new key already filled in.
Claude Desktop: Settings → Developer → Edit Config. Cursor: ~/.cursor/mcp.json. If the file
already has "mcpServers", put the xbitto entry inside it, then restart the app.
{
"mcpServers": {
"xbitto": {
"command": "npx",
"args": ["-y", "github:blackcheet/xbitto-mcp"],
"env": { "XBITTO_API_KEY": "xb_your_key" }
}
}
}Claude Code
claude mcp add xbitto -e XBITTO_API_KEY=xb_your_key -- npx -y github:blackcheet/xbitto-mcpChatGPT Desktop uses the Codex settings: add this to ~/.codex/config.toml
(Windows: %USERPROFILE%\.codex\config.toml) and restart ChatGPT.
[mcp_servers.xbitto]
command = "npx"
args = ["-y", "github:blackcheet/xbitto-mcp"]
startup_timeout_sec = 120
[mcp_servers.xbitto.env]
XBITTO_API_KEY = "xb_your_key"Grok Build: add this to ~/.grok/config.toml, then check it with grok mcp doctor xbitto.
[mcp_servers.xbitto]
command = "npx"
args = ["-y", "github:blackcheet/xbitto-mcp"]
env = { XBITTO_API_KEY = "xb_your_key" }
startup_timeout_sec = 120The first start downloads the server from GitHub, so it can take a little longer. On Windows, if an app
can't start npx, use "command": "cmd" with "args": ["/c", "npx", "-y", "github:blackcheet/xbitto-mcp"].
To stay on one version, add a tag: github:blackcheet/xbitto-mcp#v0.1.0.
Tool | What it does |
| The account the key belongs to, and what it can create right now: links left today, wallets, Bunny, credits, the Sales Fee |
| Your payout wallets (paywalls use their ids) |
| Your links and their paywall settings |
| A short link to a URL (its destination can't be changed later) |
| Tag a link, Codes item or Content item, or remove its tag |
| Your store (My Store), its tags, logo address, Telegram username and FAQ; show a paid item on it or take it off (which also ends its Featured place) |
| Sell a link: price, title, description, cover and an optional access code |
| Sell codes (accounts, license keys, proxies, gift cards), each consumer getting their own: created with its codes, from a list or a text file |
| Add codes to an item's stock, up to 1000 in one call, 100 per request |
| Change an item's price, title, label, how many codes one order can buy, or its note |
| Your Codes items and how many codes each has left, sold and owed |
| Sell 1–20 pictures from a folder |
| Finish a gallery whose upload was cut off, or add pictures to it |
| Sell a video, with an optional preview clip |
| Sell a drama of up to 100 episodes for one price, first few free |
| Add episodes to the end of a drama |
| Follow an upload running in the background |
| Your galleries, videos and dramas, and whether they are ready |
| Your orders |
| Decide a payment on hold (only when you say so) |
Every tool that sells something also takes translations: the title and description again in other
languages (en, zh, tr, vi, th, es, pt). Consumers see the one in their language; any other language shows the
main title and description, and so do share previews.
Example prompts:
"Sell the keys in keys.txt as Pro License Keys, 9 USDT each, redeemed at https://example.com/redeem."
"Upload the episodes in D:\Drama\Night Train as a drama called Night Train, 3 USDT, first 2 free."
"Add a Spanish title and description to my Night Train drama."
Uploads run in the background, so a long drama doesn't block the agent: it starts the upload and checks
progress with get_upload_job. Uploads stop if the MCP server stops; what already arrived stays.
A dropped connection is tried again; if files still don't arrive, the job says how to send just those:
add_images for pictures, add_episodes for episodes.
An API key can't add or change payout wallets, connect Bunny, change the password, email or other account settings, open, close or rename the store, change its link, logo, Telegram, FAQ or Featured items, buy credits, pay promoters, run paid wallet checks, export or delete the account, or create other keys. Do those in the dashboard. Remove a key any time on the AI Agents page.
Keep the key secret: anyone who has it can create and change your links, Codes and Content items.
The server connects directly to api.xbitto.com and to Bunny. It doesn't use the HTTP_PROXY setting.
Xbitto isn't available in some regions, from the dashboard or from this server. See the Terms.
Variable | Default | |
| — | Required |
|
| Only for testing against another server |
npm install
npm run check # typecheck, tests, and a check that dist/ is up to date
npm run build # rebuild dist/index.js (committed, so a GitHub install needs no build)MIT
Add episodes to the end of an existing series, numbered after the ones it has. People who bought it see them too.
Inputs: code (required), episodes (required).
Add items (license keys, account logins, invite links…) to a Gated link's pool; each delivered order takes one. Give items or file (a text file, one item per line). Blank lines and repeats are dropped, items over 200 characters are skipped and counted, items already in the pool are counted, not added twice. Sent 100 at a time; a pool holds up to 1000 unused items.
Inputs: code (required), file, items.
Confirm that a payment on hold belongs to this order: the consumer gets what they bought and the sales fee is charged. Only do this after the creator has said so; it can't be undone.
Inputs: orderId (required).
Sell a gallery of 1–20 pictures (JPEG, PNG, WebP, GIF or AVIF, each at most 20 MB) from this computer. They go straight to the creator's own Bunny Storage zone. One picture is the cover (blurred or not on the landing page).
Inputs: price (required), title (required), images (required), coverIndex, +4 more.
Create a short link to a destination URL. Its destination can never be changed afterwards. To sell it, call set_paywall on it next.
Inputs: targetUrl (required).
Sell a series of episodes (a short drama or web series) for one price, with the first few free. Up to 100 episodes from this computer, numbered in the order given (a folder: natural name order). Files go straight to the creator's Bunny Stream library. It takes orders once at least freeCount + 1 episodes (and at least 2) are ready.
Inputs: price (required), title (required), episodes (required), freeCount (required), +6 more.
Sell a video from this computer, with an optional short preview clip that plays on the landing page. Files go straight to the creator's own Bunny Stream library; the item takes orders once Bunny has finished encoding the main video.
Inputs: price (required), title (required), video (required), description, +4 more.
One link with its paywall settings.
Inputs: code (required).
One order, with the payment under review if there is one.
Inputs: orderId (required).
How many items a Gated link's pool has left and how many were given to orders.
Inputs: code (required).
How an upload started by create_gallery, create_video, create_series or add_episodes is going. Without jobId: the recent jobs.
Inputs: jobId.
One Vault item: its state (uploading, processing, ready), paywall and, for a series, how many episodes are ready.
Inputs: code (required).
The account's links, newest first, ten a page. Pass nextCursor back as cursor for the next page.
Inputs: q, tag, kind, cursor, +1 more.
The account's orders, newest first, ten a page. 'hold' are payments waiting for the creator's decision (confirm_payment / reject_payment).
Inputs: cursor, status.
The account's Vault items (galleries, videos, series), newest first, ten a page.
Inputs: cursor.
The account's payout wallets. Paywalls take their ids (one per network). Wallets can only be added in the dashboard.
Inputs: no named parameters.
Reject a payment on hold: the order is not delivered. Only do this after the creator has said so; it can't be undone.
Inputs: orderId (required).
Turn a link into a Gated link (or update its paywall): consumers pay to get the destination and, optionally, an access code. Replaces the paywall's settings, so pass every field you want kept. For one code per order use codeMode 'unique' and fill the pool with add_pool_items.
Inputs: code (required), price (required), title (required), codeMode, +7 more.
The Xbitto account this API key belongs to, and its credit balance.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 19 tools
Each tool targets a distinct resource and action: links, vault items, paywalls, pool items, uploads, orders, and payments are clearly separated. Minor potential overlap between get_upload_job and get_vault_item is resolved by their descriptions, which distinguish upload progress from item state.
Most tools follow a consistent verb_noun pattern: list_vault, get_link, create_video, add_episodes, confirm_payment, etc. The only notable deviation is whoami, which breaks the convention but remains clear.
With 19 tools, the set is slightly above the typical 3–15 range, but the platform covers multiple resource types and workflows. Each tool has a clear, distinct role, so the count is reasonable rather than bloated.
Core lifecycle operations are covered: content creation for galleries/videos/series, link and paywall setup, pool management, upload tracking, and order/payment decisions. Some gaps exist around deleting or editing links and vault items, but agents can work around these limitations for most workflows.
Upload, generate, organize, search, and transform images, videos, and files with AI-powered tools.
LLM chat, text tools, image generation, editing, batch image jobs, and asynchronous video generation
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Image and video AI tools and your own pipelines, run from any AI assistant.
