TikTok trends in VS Code

TikTok trends reach VS Code through Trends MCP in Copilot Chat, not through Cursor’s transport field and not through Cline’s Remote Server block. Command Palette MCP: Add Server, or a workspace file under servers in .vscode/mcp.json. type must be http. url must be https://api.trendsmcp.ai/mcp. Then Chat can call get_top_trends type TikTok Trending Hashtags or TikTok Trending Searches, and get_growth source tiktok. Default limit 25.

Generic VS Code: Trends MCP for VS Code. Google combo in the same editor: Google Trends MCP for VS Code. Cursor TikTok: TikTok trends in Cursor. Hashtag contract: TikTok trending hashtags API.

Copilot Chat versus Cline

Copilot Chat is the caller this page means. Inline completions are not. Cline is not. Continue and other chat extensions may read MCP on their own rules. If Chat cannot see tools, confirm the MCP view shows the server started, Copilot is the selected participant, and the folder is trusted.

"trends-mcp": {
  "type": "http",
  "url": "https://api.trendsmcp.ai/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

Key from the account page. User-level MCP config is the better home for the live token. Workspace .vscode/mcp.json is the better home for the server name the team shares. Mixing a production key into a public template is a leak.

Say “using TrendsMCP.” Chat that only has browsing will retrieve Creative Center folklore.

Two TikTok boards, one editor

get_top_trends(type="TikTok Trending Hashtags", limit=25)
get_top_trends(type="TikTok Trending Searches", limit=25)
get_growth(keyword="standing desk", source="tiktok", percent_growth=["30D"])

Hashtags are not searches. History source is tiktok. Sending type TikTok Trending Hashtags into get_growth is invalid_source. sort rank_change needs a baseline snapshot. Cross-check Google with a second source on the same keyword. That is a second request.

Do not freeze this morning’s hashtags in .vscode snippets. The board turns over. Cite as_of_ts.

Virlo still wins handles and sounds. Keep it in Cline or Chat if the ticket names @. Trends MCP will not invent follower counts cleanly.

Quotas inside the IDE

Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Pricing. A sequence that works: one hashtag board, one tiktok growth call. Two requests. A sequence that fails: limit 200 on both boards, then ten growth names, then a web search “to confirm.”

Empty: not_found or data_unavailable. Low-volume percents: quote both index values. 401: www OAuth URL in this file.

VS Code is a weak cron. Nightly hashtag tracking belongs on REST. Official VS Code MCP docs teach servers and type. They do not rank a TikTok index. This URL exists so the combo title matches.

If Agent-style Chat starts quoting view counts, stop. Those fields are not in this payload. Open Creative Center or TikTok Analytics. Mixing the two without labels produces a review comment that looks cited and still lacks a recent_date.

Workspace trust, two JSON files, one key

Restricted mode in VS Code can hide MCP until the folder is trusted. That failure looks like “TikTok MCP does not work” when the editor is protecting the workspace. Trust the folder, confirm the MCP view shows Trends MCP started, then retry Chat.

User-level config can hold the live tmcp_live_ key. Workspace .vscode/mcp.json can ship the server name. Cline’s Remote Server object is a third place. Copilot Chat will not see Cline’s object. Cline will not see Copilot’s type http block unless someone duplicated it. Two callers, two shapes, one Trends MCP account.

A proving pair that fits the free plan: one TikTok Trending Hashtags page, one get_growth source tiktok. Two requests. Searches are a third object if the ticket named queries. Google Search is a fourth source if the ticket asked “is this only TikTok.” Cap it.

.vscode snippets can pin the two type strings. They should not pin this morning’s hashtags. The board turns over.

Nightly hashtag tracking still belongs on REST. POST https://api.trendsmcp.ai/api with mode get_top_trends. The IDE does not need to stay open. Using Copilot Chat as a personal Creative Center is how the free 100-request plan expires while nobody is coding.

Empty series on a later growth call is not a failed connect. The board already proved the server. not_found means that keyword-plus-source pair has no points. Fail closed.

If the next turn is a handle, stop using Trends MCP. Virlo or Creative Center owns creator objects. This Chat path stays public boards. Copilot Chat is the caller this page means. Inline completions are not. Continue may read MCP on its own rules. Confirm the participant before blaming the API. A trusted folder with a started server and a named prompt is the proving path. Nightly tracking still belongs on REST. Connecting is free. Calling is not. Invented view counts in a review comment are worse than an empty tool list. Official VS Code MCP docs teach servers and type. They do not rank a TikTok index. Cline docs teach Remote Server url. They do not either. This URL exists so the combo title matches. After Copilot Chat returns as_of_ts, the connect is done. Extra boards are extra requests. Cap the prompt. Nightly tracking belongs on REST, not on Chat left open overnight.

Cline in the same window is a second client. It wants url plus headers and no type. Copilot Chat wants .vscode/mcp.json with type http. Pasting one JSON into the other is why tools vanish. Diff against Trends MCP for VS Code before opening a ticket. A trusted workspace still needs the server started. A grey row is not a live Bearer.