Xbitto MCP
Related Servers
Alternatives to Xbitto MCP
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenanceExposes native OnlyFans and Fansly access as MCP tools, letting agents read fans, messages, media, earnings, posts, transactions and subscribers across connected creators, with opt-in outbound writes. It also provides CRM tags, smart links, webhooks and bulk exports through a single API key.MIT
SpicyAPI MCP Serverofficial
AlicenseAqualityBmaintenanceOfficial MCP server for SpicyAPI, an unrestricted AI API with no platform content filter: browse 200+ image, video, audio and chat models, get exact USD quotes, upload local files, create generation tasks and collect results, with a confirmation before every paid step.15415 npm1MIT- FlicenseNot gradedqualityDmaintenanceEnables agents to manage a creator business on the vips platform, including posting content, managing subscriptions, handling payments, and going live. Provides tools for earnings, analytics, and subscriber management via MCP tools.53 npm-
- AlicenseBqualityBmaintenanceEnables AI clients to discover current fal.ai model schemas and pricing, submit only approved generation batches, manage assets, collections, tags, characters, and CDN access settings, and use isolated private account profiles through shared validated tools.66100 npmAGPL 3.0

Ronana MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI apps to browse models, estimate costs, generate and upscale images or videos, retrieve generations, and manage library references, uploads, folders, and account details, with optional uploading of local files from a configured directory.1,857 npmMIT
Longwaveofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to turn long-form episodes into Shorts, thumbnails, show notes and a podcast RSS feed, then publish them to the creator's own YouTube channel using OAuth-based, credential-free access. It exposes a deny-by-default set of read, create and step-up-approved publish tools so agents can run a creator's clip pipeline end to end without holding API keys or Google credentials.1MIT
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.