for personal agents

Your agent gets a Xiaohongshu link. Now it can read it.

Muse, Grok Bot, Manus Cue, Hermes, OpenClaw, Claude Code and Cursor all take an MCP server or a skill. Add LinkDigest once and every Xiaohongshu, Douyin, TikTok, YouTube, X or WeChat-article link your user pastes comes back as text: transcript, on-screen text, every image read, key points with checked quotes, and a receipt of how much was read. $0.02 an image post, $0.02 per minute of video, 10 free on sign-up.

sign in, no key to paste

ChatGPT and Claude: add a connector

Add https://linkdigest.dev/mcp/oauth as a connector and choose OAuth. You sign in to LinkDigest (or sign up, with 10 free credits), approve the app once, and it reads links on your own account. Revoke it any time in API keys.

ChatGPT

  1. Turn on Developer mode: Settings → Apps → Advanced settings (your plan and workspace decide whether it is offered).
  2. Create an app: MCP server URL https://linkdigest.dev/mcp/oauth, Authentication OAuth, client ID left empty.
  3. Sign in to LinkDigest in the window that opens and press Approve.

claude.ai, Claude Desktop, Claude Code

  1. claude.ai / Desktop: Settings → Connectors → Add custom connector, URL https://linkdigest.dev/mcp/oauth, then Connect.
  2. Claude Code: claude mcp add --transport http linkdigest https://linkdigest.dev/mcp/oauth, then /mcp → Authenticate.
  3. Sign in to LinkDigest and press Approve.

Cursor · VS Code (one click)

  1. Cursor: Add to Cursor. Cursor asks to confirm the install; then sign in to LinkDigest from its MCP settings.
  2. VS Code: run code --add-mcp '{"name":"linkdigest","type":"http","url":"https://linkdigest.dev/mcp/oauth"}' in a terminal, then start it from the MCP server list.
  3. Sign in to LinkDigest and press Approve.

Run end to end on 2026-11-09 (sign-in, approval, token, a tool call, refresh, revoke); ChatGPT’s and Claude Code’s own client documents are accepted. A key from the console works on https://linkdigest.dev/mcp/oauth too.

no key, no sign-up

Try it from the agent first

Without a key, digest_url and POST /api/v1/digest return a summary — title, author, key points, counts — up to two a day per address. Enough to see that it works before anyone signs up.

curl -X POST https://linkdigest.dev/api/v1/digest \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.xiaohongshu.com/explore/…"}'

# a key by email, no browser:
curl -X POST https://linkdigest.dev/api/v1/keys/request \
  -H "Content-Type: application/json" -d '{"email": "you@example.com"}'

step by step

One server, every agent

Meta Muse

Meta's personal agent (September 2026), in its app, on the web and in WhatsApp.

  1. Muse uses outside services as connectors from Meta's reviewed directory (Settings → Connectors). LinkDigest is not listed there yet.
  2. Muse Code takes MCP servers as tools today: https://linkdigest.dev/mcp with the header Authorization: Bearer ld_live_… (your key).
  3. Or let Muse use the site in its own browser: linkdigest.dev/read/<link> answers without a key (a preview); a key from /app/keys reads the rest.

Meta reviews each connector (function, security, legal, an end-to-end test) before listing it, and Muse asks before it buys or sends anything.

xAI Grok Bot

Named agents on a persistent cloud computer, with connectors and MCP tools.

  1. Tell it in chat: "Add a custom MCP server called LinkDigest at https://linkdigest.dev/mcp/oauth", press Add it, then Authorize on the connect card (sign in, Approve).
  2. Or with a key: "… at https://linkdigest.dev/mcp, header Authorization: Bearer ld_live_…" — it stores the key as a header, never in the URL.
  3. Then tell the agent once: "when I send a Xiaohongshu or Douyin link, read it with digest_url first."

Grok Bot has no settings field for MCP servers: it adds them from chat, for every bot on the account, and runs the reads on its own cloud computer.

Manus Cue

Manus 2.0's personal agent with its own phone number, email and wallet.

  1. Settings → MCP → add a custom server.
  2. URL https://linkdigest.dev/mcp; Authorization: Bearer ld_live_….
  3. Cue agents take Bearer-token MCP servers the same way the published Adaptly and Flowsery connectors do.

Cue's users send it links from Chinese apps all day; this is the read it was missing.

Hermes Agent · OpenClaw

Open personal-agent frameworks with skill registries.

  1. hermes skills install clawhub/xiaohongshu-note-to-text (also douyin-video-to-text, tiktok-transcript, long-video-transcript)
  2. OpenClaw: install the same skills from ClawHub.
  3. The skill's script works without a key for a first look; set LINKDIGEST_API_KEY for the full output.

The first paying LinkDigest customer came through one of these skills.

Claude Code · Cursor · any MCP client

Coding and desktop agents.

  1. claude mcp add --transport http linkdigest https://linkdigest.dev/mcp --header "Authorization: Bearer ld_live_…"
  2. Cursor / others: a streamable-HTTP MCP server at https://linkdigest.dev/mcp with the same header.
  3. Python, no MCP: pip install linkdigest-mcp — or POST https://linkdigest.dev/api/v1/digest.

The MCP server and the REST API run the same code and return the same digest.

Codex CLI · Gemini CLI · VS Code · Cline

Coding agents that take a remote MCP server, each in its own documented form.

  1. Codex CLI: export LINKDIGEST_API_KEY=ld_live_… then codex mcp add linkdigest --url https://linkdigest.dev/mcp --bearer-token-env-var LINKDIGEST_API_KEY
  2. Gemini CLI: gemini mcp add -s user --transport http --header "Authorization: Bearer ld_live_…" linkdigest https://linkdigest.dev/mcp
  3. VS Code, in .vscode/mcp.json: a server of "type": "http" with "url": "https://linkdigest.dev/mcp" and the same header. Cline: the same with "type": "streamableHttp".

Kiro, Trae, Windsurf and Cherry Studio take the same server; the block for each is in the README at github.com/jcaiagent7143-ui/linkdigest-mcp#install.

Checked 2026-10-08 against each agent’s own documentation or a published connector guide. No partnership is implied; LinkDigest is independent.

agent platforms

Dify, Coze, GPTBots

Teams building agents on a platform rather than in a code editor. Same server, same key.

Dify

Agent and workflow builder, self-hosted or cloud.

  1. Marketplace → search LinkDigest → install the plugin; paste your key as the provider credential.
  2. Use the digest_url tool in an agent or a workflow node (format json for structured output).
  3. A ready-made research workflow (links in → summaries and a comparison out): linkdigest.dev/docs/dify — import the DSL and run.

The plugin polls a long read for you; no job handling needed.

Coze

ByteDance's agent builder (扣子).

  1. Plugins → Create → Import from OpenAPI: https://linkdigest.dev/openapi.json.
  2. Auth: Bearer token, your ld_live_… key.
  3. Give the bot the digest_url and get_digest tools; it collects a slow read with the jobId.

Step-by-step with screenshots in the Chinese docs (#coze).

GPTBots

Enterprise bot platform with custom Tools.

  1. Tools → create a custom tool from the REST endpoint: POST https://linkdigest.dev/api/v1/digest with a JSON body { url, format }.
  2. Header Authorization: Bearer ld_live_… (your key).
  3. On 202, call GET /api/v1/digest/{jobId}?wait=20 until it answers 200.

Any platform that can call an HTTPS endpoint works the same way; the OpenAPI file describes every field.

what the agent gets back

Not a summary. A record.

Every digest carries coverage (seconds transcribed of the total, images read of the total, the largest gap between frames, what was not captured) and key_point_support — a short quote behind each key point, checked word for word against the post. Your agent can tell its user what it read and what it did not.