LamaTok — TikTok MCP
Related Servers
Alternatives to LamaTok — TikTok MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceMCP server for HikerAPI — auto-generates 100+ Instagram tools (profiles, posts, reels, stories, comments, hashtags, locations) from the live OpenAPI spec. Local stdio via npx -y hikerapi-mcp, requires only HIKERAPI_KEY.10050 npm8MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for DataLikers — 51 tools for Instagram & TikTok data: Instagram user search by demographics (gender/age/race/country/city), profiles, engagement, posts, comments, hashtags, locations, stories, business accounts; TikTok users, videos, comments, hashtags, playlists. Local stdio via npx -y datalikers-mcp, requires only DATALIKERS_API_KEY.15 npm9MIT

CutPro MCPofficial
AlicenseNot gradedqualityDmaintenanceMCP server exposing the full CutPro v1 API as 34 tools for AI clients — analyze videos, submit clipping jobs, manage clips, render, and publish posts. Supports stdio, Streamable HTTP, and OAuth 2.1.35 npm2MIT- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes FortiCNAPP (formerly Lacework) API 2.0 operations as typed, auth-aware tools generated from the API spec at startup, supporting both local stdio and remote Streamable HTTP transports.MIT
- AlicenseAqualityBmaintenanceEnables downloading TikTok videos and photos without watermarks, extracting metadata and analytics, and performing bulk downloads of user profiles via CLI or as an MCP server for AI assistants.516 npm1MIT
- AlicenseAqualityAmaintenanceSelf-hosted TikTok Ads MCP server with 35 read tools and 29 opt-in, preview-first write tools. Maintained source relocated from getmcpads-com/tiktok-ads-mcp-server; npm package remains @getmcpads/tiktok-ads-mcp-server.35323 npmApache 2.0
TDQS
Scored across 19 tools
Many tools are near-duplicates differing only by parameter (secUid vs username, id vs url). While descriptions hint at the difference, agents may confuse which parameter to use, especially for user and download tools.
All tools follow a strict 'get_v1_{resource}_{action}_by_{param}' pattern, making them highly predictable and consistent.
19 tools is slightly above average but reasonable for an API covering hashtag, media, and user resources. No tool seems unnecessary, but the number could be reduced by consolidating parameter variants.
Covers core read operations: hashtag data, media details/comments/downloads, and user info/followers/following/playlists/suggested. Missing search or write operations, but acceptable for a data extraction API.