Free TikTok Analytics MCP Server by viral.app

Created By
viral-appa year ago
Connect your AI tools to live TikTok analytics with viral.app's Model Context Protocol (MCP) server. Get real-time TikTok data directly in Cursor, Claude Desktop, Raycast, and more.
Overview

What is viral.app MCP?

viral.app MCP is a powerful bridge between your AI assistant and TikTok's analytics data. It enables your AI to access real-time TikTok insights without manual data gathering.

How to use viral.app MCP?

To use viral.app MCP, create a free account at viral.app, configure your AI client with the provided server command, and authenticate via OAuth to start analyzing TikTok data.

Key features of viral.app MCP?

  • Retrieve TikTok user profiles and statistics
  • Analyze video performance metrics
  • Get video transcripts
  • List recent videos from any profile

Use cases of viral.app MCP?

  1. Analyzing TikTok user engagement and follower growth.
  2. Evaluating video performance for marketing strategies.
  3. Gathering insights for content creation and optimization.

FAQ from viral.app MCP?

  • Is there a cost to use viral.app MCP?

No, you can start with a free account and use the MCP server without a credit card.

  • What tools can I connect with viral.app MCP?

You can connect it with Cursor, Claude Desktop, Raycast, and more.

  • How many daily tool calls are available?

The free tier allows 5 daily tool calls, with options to upgrade for more.

Server Config

{
  "mcpServers": {
    "viral.app": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://viral.app/api/mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
viral-app
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago