Xbitto MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBITTO_API_KEY | Yes | Your Xbitto API key from the dashboard under Settings → API Keys → Create Key. | |
| XBITTO_API_URL | No | Only for testing against another server. | https://api.xbitto.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | The Xbitto account this API key belongs to, and its credit balance. |
| list_walletsA | The account's payout wallets. Paywalls take their ids (one per network). Wallets can only be added in the dashboard. |
| list_linksB | The account's links, newest first, ten a page. Pass nextCursor back as cursor for the next page. |
| get_linkC | One link with its paywall settings. |
| create_linkA | Create a short link to a destination URL. Its destination can never be changed afterwards. To sell it, call set_paywall on it next. |
| set_paywallA | 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. |
| add_pool_itemsA | Add items (license keys, account logins, invite links…) to a Gated link's pool; each delivered order takes one. Give |
| get_pool_statsC | How many items a Gated link's pool has left and how many were given to orders. |
| create_galleryA | 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). |
| create_videoA | 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. |
| create_seriesA | 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. |
| add_episodesA | Add episodes to the end of an existing series, numbered after the ones it has. People who bought it see them too. |
| get_upload_jobA | How an upload started by create_gallery, create_video, create_series or add_episodes is going. Without jobId: the recent jobs. |
| list_vaultA | The account's Vault items (galleries, videos, series), newest first, ten a page. |
| get_vault_itemA | One Vault item: its state (uploading, processing, ready), paywall and, for a series, how many episodes are ready. |
| list_ordersB | The account's orders, newest first, ten a page. 'hold' are payments waiting for the creator's decision (confirm_payment / reject_payment). |
| get_orderC | One order, with the payment under review if there is one. |
| confirm_paymentA | 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. |
| reject_paymentA | Reject a payment on hold: the order is not delivered. Only do this after the creator has said so; it can't be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.