
BusyBee — Social Media Data
io.github.danfeistarPublished by GitHub account danfeistarv0.2.4Updated Nov 1, 2026
Social media data for AI agents: creators, posts, comments, insights, trending across 6 platforms.
Overview
BusyBee gives an assistant public social media data from TikTok, Instagram, YouTube, X, Douyin and Xiaohongshu through ten business-level tools with one…
- What you can do
- Discover platforms and check which tools each one supports, plus check remaining credit
- Search creators and posts by keyword on a chosen platform
- Read a creator's profile and recent posts, or fetch details of a single post
- Retrieve comments under a post and get comment insights such as sentiment split, question ratio, frequent phrases and top-liked comments
- List trending content on a platform
- Every response carries a cost and balance figure so the assistant can track spending
- When to use it
- Useful when you want an assistant to research creators, topics, trends or audience reactions across major short-video and social platforms in a single conversation, for example creator discovery, competitor monitoring or demand mining from comment sections.
- Requirements
- A remote endpoint at lucydomi.com over Streamable HTTP (legacy SSE and REST/OpenAPI also offered). A bearer API key in the Authorization header, obtained by signing up; overseas and China platforms use different key groups. A local stdio option exists via a Python package with the BUSYBEE_API_KEY environment variable. Network access required.
Installation
In SourceWeft
- Open BusyBee — Social Media Data in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.danfeistar%2Fbusybee/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"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-开头的串 - 计费:按次,每次返回都带本次花费与余额;失败不扣费
- 报错是干净中文/英文,不暴露任何上游信息
Source: README.md at commit eae1883
Tools
0Version history
3- v0.2.4LatestOct 25, 2026
- v0.2.3Oct 24, 2026
- v0.2.2Oct 23, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts