tiktok_location_posts — TikTok data for agents MCP Tool
tiktok_location_posts
(tiktok location posts) is one of 15 tools on the
TikTok data for agents
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tiktok_location_posts from your client
- Claude Code TikTok data for agents tiktok_location_posts run in your project directory
- Claude Desktop TikTok data for agents tiktok_location_posts ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TikTok data for agents tiktok_location_posts ~/.cursor/mcp.json
- VS Code TikTok data for agents tiktok_location_posts .vscode/mcp.json
- Zed TikTok data for agents tiktok_location_posts ~/.config/zed/settings.json
- Windsurf TikTok data for agents tiktok_location_posts ~/.codeium/windsurf/mcp_config.json
- Cline TikTok data for agents tiktok_location_posts ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TikTok data for agents tiktok_location_posts ~/.gemini/settings.json
- Grok TikTok data for agents tiktok_location_posts .mcp.json (in your project root)
- ChatGPT TikTok data for agents tiktok_location_posts Settings → Connectors → Advanced → Developer mode
- Claude.ai TikTok data for agents tiktok_location_posts Settings → Connectors → Add custom connector
- LangChain TikTok data for agents tiktok_location_posts pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://tiktok.fetcher.sh/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.