BusyBee MCP
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.
Endpoint https://lucydomi.com/mcp
Protocols MCP Streamable HTTP · MCP SSE (legacy) · REST/JSON · stdio
Tools 10
Billing pay per call; every response returns cost_usd + balance_usd
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.
| Your agent | What it supports | How to connect |
|---|---|---|
| Claude Code | Streamable HTTP | claude mcp add busybee --transport http https://lucydomi.com/mcp --header "Authorization: Bearer sk-..." |
| Cursor / Cline / Windsurf / VS Code | Streamable HTTP | add to mcp.json (see below) |
| Claude Desktop | stdio | uvx busybee-mcp with BUSYBEE_API_KEY |
| Older MCP clients (2024-11 era) | SSE only | https://lucydomi.com/sse + https://lucydomi.com/messages/ |
| Dify / n8n / Coze / FastGPT | OpenAPI / plain HTTP | import https://lucydomi.com/mcp/openapi.json (3.1), or ?spec=3.0 for older importers |
| LangChain / LlamaIndex / custom code | tools JSON or HTTP | https://lucydomi.com/mcp/tools?format=openai, or call REST directly |
| GPT Actions / Zapier / Make | OpenAPI 3.x | same spec URL, bearer auth |
| Anything that can only GET a URL | query string | https://lucydomi.com/mcp/v1/search_creators?platform=tiktok&keyword=coffee&api_key=sk-... |
Discovery document (machine-readable, tells an agent what's available): https://lucydomi.com/mcp/info
The 10 tools
| Tool | What it answers |
|---|---|
list_platforms |
Which platforms exist, which tools each supports, which key group you need |
search_creators |
"Find me mid-size coffee creators on TikTok" |
search_posts |
"What is being posted about cold brew this week?" |
get_creator |
"How big is this account, what's their bio?" |
list_creator_posts |
"What has this account posted recently?" |
get_post |
"Give me the details of this one video" |
get_comments |
"What are people saying under this post?" |
get_trending |
"What's trending on Douyin right now?" |
get_comment_insights |
"Summarize the comment section: sentiment, questions, complaints" |
check_balance |
"How much credit do I have left?" |
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.
One schema, every platform
{
"platform": "tiktok",
"id": "7690199760430566669",
"url": "https://www.tiktok.com/@creator/video/7690199760430566669",
"author": { "id": "6948174171005158405", "handle": "goldenbrown.coffee", "name": "Golden Brown Coffee" },
"text": "Spanish latte, but make it iced",
"created_at": "2026-10-18T09:12:00Z",
"stats": { "likes": 41200, "comments": 812, "shares": 2331, "views": 918000, "collects": 5120 },
"cover": "https://..."
}
Every response also 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
claude mcp add busybee --transport http https://lucydomi.com/mcp \
--header "Authorization: Bearer sk-YOUR_KEY"
Cursor / Cline / Windsurf / VS Code (~/.cursor/mcp.json)
{
"mcpServers": {
"busybee": {
"url": "https://lucydomi.com/mcp",
"headers": { "Authorization": "Bearer sk-YOUR_KEY" }
}
}
}
Claude Desktop (local stdio)
{
"mcpServers": {
"busybee": {
"command": "uvx",
"args": ["busybee-mcp"],
"args": ["busybee-mcp"],
"env": { "BUSYBEE_API_KEY": "sk-YOUR_KEY" }
}
}
}
Legacy SSE clients
SSE URL https://lucydomi.com/sse
Messages URL https://lucydomi.com/messages/?session_id=<from the SSE event>
Header Authorization: Bearer sk-YOUR_KEY
Dify / n8n / Coze / GPT Actions
Import https://lucydomi.com/mcp/openapi.json, set auth to Bearer sk-YOUR_KEY. If the importer rejects 3.1, use https://lucydomi.com/mcp/openapi.json?spec=3.0.
LangChain / custom Python (no MCP needed)
import json, urllib.request
req = urllib.request.Request(
"https://lucydomi.com/mcp/v1/search_creators",
data=json.dumps({"platform": "tiktok", "keyword": "coffee", "limit": 3}).encode(),
headers={"Content-Type": "application/json", "Authorization": "Bearer sk-YOUR_KEY"},
)
print(json.load(urllib.request.urlopen(req)))
Tool schemas for function calling: GET https://lucydomi.com/mcp/tools?format=openai
Local package
pip install busybee-mcp
BUSYBEE_API_KEY=sk-YOUR_KEY busybee-mcp # stdio
BUSYBEE_API_KEY=sk-YOUR_KEY busybee-mcp http # serve all transports on :3013
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
error |
Meaning | What to do |
|---|---|---|
no_api_key |
No key supplied | Add Authorization: Bearer sk-..., X-API-Key, or ?api_key= |
unauthorized |
Key invalid or deleted | Issue a new key in the console |
insufficient_balance |
Out of credit | Top up |
forbidden |
Key group doesn't cover that platform | Create a key in the right group |
rate_limited |
Too many requests | Back off and retry |
unsupported_tool |
That platform doesn't expose the tool | Call list_platforms to see the matrix |
upstream_error |
Temporary provider failure | Retry once; not billed |
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 个业务级工具 + 一套统一字段,同一台服务器支持四种接入方式:
| 你的 AI 工具 | 接入地址 |
|---|---|
| Claude Code / Cursor / Cline(MCP 新版) | https://lucydomi.com/mcp |
| 只认旧版 SSE 的客户端 | https://lucydomi.com/sse |
| Dify / n8n / Coze / GPT Actions(OpenAPI) | https://lucydomi.com/mcp/openapi.json |
| 任何能发 HTTP 的程序 | https://lucydomi.com/mcp/v1/<工具名> |
- 密钥:注册后在控制台建
sk-开头的串 - 计费:按次,每次返回都带本次花费与余额;失败不扣费
- 报错是干净中文/英文,不暴露任何上游信息
Metadata
Release files for busybee-mcp 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| busybee_mcp-0.2.2.tar.gz | 33.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| busybee_mcp-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.2 kB
Release files / busybee_mcp-0.2.2.tar.gz
| Download URL | busybee_mcp-0.2.2.tar.gz |
|---|---|
| Size | 33.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e981ab580921929d81279f58e9c4506c4d2d831f33921ffc7a72974d14013345
|
|
BLAKE2b-256 checksum How to use checksums |
f3f609abd6669d96782ae1e7b7f7ab2dfae4bf0ce611854c4b1eb798907cc995
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / busybee_mcp-0.2.2-py3-none-any.whl
| Download URL | busybee_mcp-0.2.2-py3-none-any.whl |
|---|---|
| Size | 33.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f2ddcbb125cd0151fe5f4f023c51a432e346dc11eb951e7f244fb7bdbfe9a04
|
|
BLAKE2b-256 checksum How to use checksums |
77030edb8604257697513fed2b8aefea3e40df97eb6a9954e2c9c27b4c1e9c34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for busybee-mcp 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.