MCP Directory
Back to Blog
douyin-tiktok-download-apimcp-servertiktok-scraperdouyin-downloaderno-watermark

Douyin_TikTok_Download_API MCP Server: Self-Hosted No-Watermark Scraper

November 7, 2026
3 min read

Douyin_TikTok_Download_API MCP Server: Self-Hosted No-Watermark Scraper

Douyin_TikTok_Download_API provides a self-hosted solution for scraping and downloading content from Douyin and TikTok. Written in Python, this project offers a suite of interfaces including an async REST API, a CLI, a web console, and an MCP server, all designed to collect posts, profiles, comments, and playlists. It focuses on providing watermark-free video downloads by accessing the clean streams already published by the platforms, and archives collected data in PostgreSQL.

Core Capabilities and Deployment

This server is designed for local deployment, typically via docker compose up, which sets up the entire stack including a self-healing identity pool and PostgreSQL for data storage. Key capabilities include:

  • Parsing: Handles various input formats such as direct links, share text, short links, or bare post IDs.
  • Archiving: Stores all parsed content, ensuring data persistence even if posts are removed upstream.
  • Downloading: Facilitates bulk media downloads by author, skipping existing files and performing duplicate cleanup.
  • Watching: Monitors specific authors or posts, re-collecting content on a configurable timer.
  • iOS Shortcut Support: Integrates with iOS Shortcuts via a dedicated API endpoint at /api/v1/ios/shortcut.

The project maintains an identity pool that manages itself, removing the need for manual signup or quota management often associated with third-party APIs.

MCP Integration and Access Points

Douyin_TikTok_Download_API exposes its functionality through multiple entry points, with the MCP server being a primary one. The service layer is shared across all interfaces, ensuring consistent behavior.

Here's how you can access the server:

  • Web Console: Available at the root path (/), offering a UI for the identity pool, scheduler, library, downloads, logs, and diagnostics.
  • API Reference: Swagger UI is accessible within the console at /docs, with bare references also available at /swagger and /redoc without login.
  • REST API: Provides 93 operations under the /api/v1/... path.
  • MCP Server: Accessible at /mcp. Client setup instructions are provided within the console at /mcp-guide.
  • CLI: The command-line interface, dtk, offers the same capabilities as the other entry points.

For developers integrating with MCP, the /mcp endpoint is where the protocol server resides. The /mcp-guide in the web console is the first place to look for specific client setup instructions, detailing how to connect and leverage the server's data collection and download features within an MCP client environment.

References

Back to all posts