
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 分