Official viral.app plugins and install shortcuts for coding agents and chat apps. One install connects your agent to the viral.app MCP server: 100+ tools for UGC analytics, account and video tracking, tags and tag workflows, the Creator Hub (campaigns, briefs, job postings, applications, creator chat, payouts), the viral video library, and live TikTok/Instagram/YouTube/Facebook lookups. Plugins also bring that teach the agent the workflows.
UGC analytics and Creator Hub for TikTok, Instagram and YouTube: tracking, campaigns, jobs, events.
The MCP server lives at https://viral.app/api/mcp (streamable HTTP, OAuth). You need a viral.app account with API access. Manage everything at viral.app/app/org/api/agents.
Install
Every client signs in with OAuth in your browser. viral.app supports dynamic client registration, so you never paste a client ID, secret, or API key. During consent you pick one organization.
Cards: results render as interactive cards in the chat; ChatGPT desktop also offers viral.app as a sidebar app with a conversation panel.
Events: in Work chats (ChatGPT web, or the desktop app with Cloud selected) and in dots, ask ChatGPT to watch viral.app for something and say what to do, for example "Whenever a creator applies to my Habit Tracker job, summarize the application and draft a reply for me to approve." ChatGPT subscribes through viral.app's MCP Events and viral.app delivers each matching event to that chat. Chat, application and payout events arrive within about a minute; new-video and view-milestone events follow each account's sync cadence (hours). Ask ChatGPT to stop monitoring to end a subscription.
Grok
On grok.com, open Connectors, choose New Connector, then Custom, and paste https://viral.app/api/mcp.
For Grok Bot, install viral.app from its Marketplace once it is listed there.
Other chat apps
These accept a custom remote MCP URL with OAuth. Use https://viral.app/api/mcp:
Mistral Vibe (formerly Le Chat), Work mode: Connectors, Add Connector, Custom MCP Connector. Only admins can add connectors; use a name without special characters, such as viralapp.
Notion custom agents (Business and Enterprise): an admin enables custom MCP servers under Settings, Connections. Then open the agent's Tools & Access, Add connection, Custom MCP server.
Plugins
Claude Code
claude plugin marketplace add https://github.com/fmd-labs/viral-app-agents
claude plugin install viral-app@viral-app
Or interactively: /plugin marketplace add https://github.com/fmd-labs/viral-app-agents, then /plugin install viral-app. Afterwards run /mcp, pick viral_app, and authenticate in the browser. The fmd-labs/viral-app-agents shorthand also works if you have GitHub SSH access.
Or interactively: /plugins in the Codex TUI. Start a new session afterwards, then authenticate with codex mcp login viral_app.
Requires Codex CLI 0.147 or newer. Older versions fail the OAuth login with an "Authorization server response missing required issuer" error (a Codex bug fixed in 0.147.0); update with npm install -g @openai/codex@latest and retry.
If you only want the MCP server without the plugin:
In the CLI: goose configure, Add Extension, Remote Extension (Streamable HTTP), URL https://viral.app/api/mcp.
To add the skills as well, run goose plugin install https://github.com/fmd-labs/viral-app-agents.git. Goose loads them as viral-app:viral-app-mcp, viral-app:ugc-reporting, and so on.
Zed
Add to your Zed settings, or use Settings, AI, MCP Servers, Add Server, Add Remote Server:
Point the client at https://viral.app/api/mcp with streamable HTTP and OAuth. The server publishes standard OAuth discovery metadata and supports dynamic client registration, so no pre-shared credentials are needed. Its official MCP Registry name is io.github.fmd-labs/viral-app.
Skills
Plugins bundle seven skills. Agents load them on demand, and each keeps longer material in a references/ folder next to it.
Skill
Use it for
viral-app-mcp
The core guide: connecting and auth, the credit quote-then-confirm flow, rules for writes that reach creators, ids and units, what MCP cannot do, and which skill to load next
ugc-reporting
Weekly or monthly UGC reports, KPI and leaderboard recipes with period-over-period change, cards in Claude and ChatGPT, Slack summaries, recurring reports through scheduled tasks or a ChatGPT page
creator-briefs
Creator briefs the way viral.app's Copilot writes them: the product, proven sample videos from the viral library or your own videos, the brief's structure, numbered samples, who reads it and whether to notify; MCP or the REST API with an API key
creator-management
The creator roster day to day: adding creators one by one or from a CSV, invitations, linking social accounts, direct and group chats, broadcasts, nudges for stuck creators, and roster audits; MCP or REST
creator-campaigns
Creator Hub end to end: guided campaign setup with benchmarks and the preview step, pay changes and custom rates, creator assignment, job postings (writing, benchmarks, publishing), applications, and payout reads
viral-research
The viral video library, similar videos, hook and scene breakdowns, AI analysis of tracked videos, live lookups, and turning findings into hooks and a brief
ugc-automations
"Watch for X and do Y": MCP Events in ChatGPT, polling fallbacks for other clients, latency per event, and handling untrusted creator text
Agent Plugins 1.0 manifest for the repository root (Kiro, Mistral Vibe, and Copilot CLI or Devin when the repository root is installed directly; Goose imports only the skills)
mcp.json
Agent Plugins 1.0 MCP config for the repository root (read with plugin.json)
skills/
Copy of the plugin skills for the root-level packages (Gemini CLI, Agent Plugins). Generated from plugins/viral-app/skills/ with scripts/sync-skills.sh
server.json
Official MCP Registry entry io.github.fmd-labs/viral-app
.github/workflows/publish-mcp-registry.yml
Validates server.json on pull requests and publishes it to the MCP Registry from main via GitHub OIDC
plugins/viral-app/.claude-plugin/plugin.json
Claude-format plugin manifest with the MCP server inline (Claude Code, Copilot CLI, VS Code, Devin, Grok Build)
plugins/viral-app/.codex-plugin/plugin.json
Codex plugin manifest
plugins/viral-app/.cursor-plugin/plugin.json
Cursor plugin manifest
plugins/viral-app/.mcp.json
Claude-format MCP config (Codex, Factory, Grok Build; Claude Code merges it with the inline entry)
plugins/viral-app/skills/
The seven skills (canonical copy)
scripts/sync-skills.sh
Copies plugins/viral-app/skills/ to skills/; --check fails when they differ
scripts/build-chatgpt-package.sh
Builds dist/viral-app-chatgpt.zip for OpenAI's plugin dashboard (Upload new version): the Codex manifest, .mcp.json, skills and assets of plugins/viral-app, checked against OpenAI's package rules, without the Claude and Cursor manifests
plugins/viral-app/assets/
Plugin logo (logo.svg, logo.png at 400x400)
When releasing:
Bump the viral-appversion together in plugin.json, gemini-extension.json, plugins/viral-app/.claude-plugin/plugin.json, plugins/viral-app/.codex-plugin/plugin.json, plugins/viral-app/.cursor-plugin/plugin.json, and its entries in .claude-plugin/marketplace.json and .agents/plugins/marketplace.json (grep -rn '"version"' --include=*.json . lists them).
Edit skills only in plugins/viral-app/skills/, then run scripts/sync-skills.sh (--check verifies the copies match).
For ChatGPT, run scripts/build-chatgpt-package.sh and upload dist/viral-app-chatgpt.zip as a new version in the OpenAI plugin dashboard. The script writes the published plugin's package name (app-6a8713d41dc48191b33e75c49a764db3) into the ZIP's manifest, because the dashboard refuses any other name. Changes to the hosted MCP server need no upload; manifest and skill changes do.
server.json has its own version; the MCP Registry rejects a version it has already published, so bump it with every change to that file.
Auth and security
OAuth is the default. During consent you pick one organization; the grant is scoped to it permanently. Review or revoke authorized clients at viral.app/app/user/settings/security.
API keys are only for advanced setups where one agent must switch between multiple organizations. Create them per organization in the viral.app dashboard.
This repository contains no secrets and never will. It only ships public configuration pointing at the viral.app endpoint; all credentials are issued at runtime through OAuth in your own browser.
Tools that spend viral.app credits (live lookups, refreshes, video analysis) quote their cost first and only execute when called again with explicit confirmation.