Tiktok Agent Publisher vs Lurk — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Tiktok Agent Publisher vs Lurk
In-depth architectural comparison of the Tiktok Agent Publisher and Lurk MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Tiktok Agent Publisher
Social Media · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Lurk
Social Media · Local stdio
Quality: 27/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Tiktok Agent Publisher if you need specialized Social Media tools running via a local process. Choose Lurk if your workspace requires Social Media integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Tiktok Agent Publisher when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TIKTOK_CLIENT_KEY, TIKTOK_CLIENT_SECRET, TIKTOK_ACCESS_TOKEN, TIKTOK_REFRESH_TOKEN, PUBLIC_MEDIA_BASE_URL, SUPABASE_STORAGE.
Primary tools included: Dry-run mode by default to prevent unintended live posts, OAuth readiness and token presence checks, Structured JSON output for agent workflows and auditing.
Local-first TikTok Content Posting API MCP and CLI for agents, with OAuth readiness checks, dry-run publish flows and live uploads only when explicitly enabled.
Reddit reader for LLMs — full comment trees, 94% fewer tokens, one binary
Tiktok Agent Publisher is categorized under Social Media and uses a local stdio subprocess. In contrast, Lurk belongs to Social Media using local stdio subprocess. Select Tiktok Agent Publisher when you need capabilities focused on social media and Lurk when you require tools for social media.