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

Same field names whether the item came from TikTok, Instagram, YouTube, X, Douyin or Xiaohongshu:

{
  "ok": true, "platform": "tiktok", "tool": "search_posts", "count": 6,
  "items": [
    {
      "platform": "tiktok",
      "id": "7690199760430566669",
      "url": "https://www.tiktok.com/@laceyglasley/video/7690199760430566669",
      "author": { "id": "7066058701889012782", "handle": "laceyglasley", "name": "Lacey" },
      "text": "Salted Honey Spanish Latte … #coffeetok #spanishlatte",
      "created_at": "2026-09-27T13:03:24+00:00",
      "stats": { "likes": 68357, "comments": 165, "shares": 7691, "views": 1009685, "collects": 17806 },
      "cover": "https://…"
    }
  ],
  "cost_usd": 0.003, "balance_usd": 3.93
}

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

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 the OpenAPI schema, set auth to Bearer sk-YOUR_KEY. If the importer rejects 3.1, use the 3.0 view.

Platform	Where to paste	URL
Dify	Tools → Custom → Add OpenAPI tool	https://lucydomi.com/mcp/openapi.json?spec=3.0
n8n	HTTP Request node, or import as a credential-protected API	https://lucydomi.com/mcp/openapi.json
Coze	Plugin → Import from OpenAPI	https://lucydomi.com/mcp/openapi.json?spec=3.0
OpenAI GPT Actions	Actions → Import from URL	https://lucydomi.com/mcp/openapi.json

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)

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 / stats mean 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_usd on 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- 开头的串
• 计费：按次，每次返回都带本次花费与余额；失败不扣费
• 报错是干净中文/英文，不暴露任何上游信息