
BusyBee — Social Media Data
io.github.danfeistar由 GitHub 帳號 danfeistar 發布v0.2.4更新於 Nov 1, 2026
Social media data for AI agents: creators, posts, comments, insights, trending across 6 platforms.
概覽
BusyBee 讓助理透過十個業務級工具與統一欄位,取得 TikTok、Instagram、YouTube、X、抖音、小紅書的公開社群媒體資料。
- 可以做什麼
- 查詢可用平台及各平台支援哪些工具,並查看剩餘額度
- 依關鍵字在指定平台搜尋創作者與貼文
- 讀取創作者資料與近期貼文,或取得單一貼文詳情
- 取得貼文留言,並產生留言洞察,例如情緒分布、提問比例、高頻詞句與按讚最多的留言
- 查看某平台的熱門內容
- 每次回應都附上本次花費與餘額,方便助理自行控管預算
- 適用情境
- 適合需要助理在同一次對話中跨主流短影音與社群平台調查創作者、話題、趨勢或受眾反應的情境,例如發掘創作者、競品監測、從留言區挖掘需求。
- 執行需求
- 遠端端點 lucydomi.com,使用 Streamable HTTP(另提供舊版 SSE 與 REST/OpenAPI)。需註冊取得 API 金鑰,放在 Authorization 標頭中;海外平台與中國平台使用不同的金鑰群組。也可透過 Python 套件以本機 stdio 執行,使用 BUSYBEE_API_KEY 環境變數。需要網路連線。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 BusyBee — Social Media Data,將其新增到工作區。
- 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.danfeistar%2Fbusybee/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"busybee-social-media-data": {
"type": "http",
"url": "https://lucydomi.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
BusyBee MCP
[PyPI] [Python] [License: MIT] [Glama score] [BusyBee MCP on AI Agents Listing] [MCP Registry]
Public social media data for AI agents. Ten business-level tools, one schema — TikTok, Instagram, YouTube, X (Twitter), Douyin and Xiaohongshu.
Ask your agent "who are the fastest-growing coffee creators on TikTok right now, and what do their comment sections complain about?" — it answers with real data, in one conversation.
Try it in 30 seconds — no signup: open https://lucydomi.com/demo, type a keyword, see the real response shape (6 free calls per device per day, 3 of them on Douyin/Xiaohongshu). When you want unlimited calls, grab a key at https://lucydomi.com/sign-up.
Connect your agent
Step-by-step guides, each with a config file you can copy verbatim:
- Claude Desktop / Claude Code — local stdio via
uvx - Cursor / Cline / Windsurf / VS Code — remote HTTP with a bearer header
- Dify / n8n / Coze / FastGPT — import the OpenAPI spec, no code
- Plain HTTP / curl / any language — REST endpoints and the tools JSON
Works with every kind of agent
Most "social data for AI" products ship one transport and hope your client speaks it. This server speaks four, on the same host, with the same 10 tools behind all of them.
Discovery document (machine-readable, tells an agent what's available): https://lucydomi.com/mcp/info
The 10 tools
get_comment_insights is the one people keep open: it samples comments, then returns sentiment split, question ratio, high-frequency phrases and top-liked comments — so the agent answers "what do users actually want" instead of dumping fifty raw rows.
Docs by platform, by tool, by client
Each page carries a real captured response and copy-paste code, so you can skip the README once you know what you need:
Tutorials — end-to-end workflows with real numbers: mine demand from comments · build a creator database · cross-platform topic check · competitor monitoring
All 21 in one index: https://lucydomi.com/resources · machine index: https://lucydomi.com/llms.txt · everything in one file for LLMs: https://lucydomi.com/llms-full.txt
Cookbook — three scripts you can run right now
Stdlib only, no dependencies. Each was run against the live API before being committed; the output below is real.
Note the Instagram row: it reports the gap instead of silently returning nothing — list_platforms tells your agent which tools each platform actually supports, so cross-platform jobs degrade instead of breaking.
One schema, every platform
Same field names whether the item came from TikTok, Instagram, YouTube, X, Douyin or Xiaohongshu:
This is a real response, not a mock-up — captured from a live call, only the share URL query string and the caption were trimmed. Two full raw responses are checked in:
examples/1_tiktok_coffee.json (search_posts) and
examples/2_youtube_insights.json (comment insights on 20 comments).
Every response carries cost_usd and balance_usd, so the agent can budget itself and you can see what a task actually cost.
Setup per client
Need a key first: register at lucydomi.com → Console → API Keys → New key (sk-…). Overseas and China platforms use different key groups.
Claude Code
Cursor / Cline / Windsurf / VS Code (~/.cursor/mcp.json)
Claude Desktop (local stdio)
Legacy SSE clients
Dify / n8n / Coze / GPT Actions
Import the OpenAPI schema, set auth to Bearer sk-YOUR_KEY. If the importer rejects 3.1, use the 3.0 view.
Server-side endpoints derive automatically from the schema; each operation maps 1:1 to a tool name, so search_posts in the schema is POST https://lucydomi.com/mcp/v1/search_posts.
LangChain / custom Python (no MCP needed)
Tool schemas for function calling: GET https://lucydomi.com/mcp/tools?format=openai
Local package
Design decisions worth knowing
- Ten tools, not a thousand. Call a business intent, not an endpoint. The more tools a model sees, the more often it picks wrong and burns money.
- Normalized fields.
author / text / created_at / statsmean the same thing on every platform. - One implementation behind every protocol. MCP, SSE and REST share the same dispatch layer, so behavior can't drift between clients.
- Pay per call, priced per endpoint. Cheap calls cost fractions of a cent. Price is visible in your console.
- Cost transparency inside the result.
cost_usd+balance_usdon every response. - Failures are not billed.
- Clean errors. No stack traces, no third-party vendor names, no upstream documentation links leaking into your agent's context.
- CORS enabled, so browser-based agents and web widgets can call it directly.
Errors
Scope and compliance
BusyBee serves public social media data only, and only to users outside mainland China. Do not use it to profile private individuals, scrape private accounts, manipulate engagement, or train models on personal data without a lawful basis. See the data policy.
License
MIT — see LICENSE. This repository is the client-side MCP server; the hosted service is metered separately.
中文速览
BusyBee MCP 把 TikTok、Instagram、YouTube、X、抖音、小红书六个平台的公开数据,压成 10 个业务级工具 + 一套统一字段,同一台服务器支持四种接入方式:
- 密钥:注册后在控制台建
sk-开头的串 - 计费:按次,每次返回都带本次花费与余额;失败不扣费
- 报错是干净中文/英文,不暴露任何上游信息
來源:README.md,提交 eae1883
工具
0版本歷史
3- v0.2.4最新Oct 25, 2026
- v0.2.3Oct 24, 2026
- v0.2.2Oct 23, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分