Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
ViralCat is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
21
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Schedule and publish social posts across platforms, with drafts, media uploads and analytics.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http viralcat-mcp https://viral-cat.com/api/mcp/mcp
# 2 — ask your agent for something these tools do
# list_brands, get_brand_details, list_posts and 18 more
ViralCat costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VCAll 1 server
viral-cat1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http viralcat-mcp https://viral-cat.com/api/mcp/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List brands (content profiles), newest first, with per-brand post counts (posted/scheduled) and the next scheduled date. Use to see which brands exist and how active each is. Excludes archived brands. Returns total (all active brands) next to count (rows returned): when truncated is true the roster was cut off by limit, so raise it (max 50) before concluding a brand does not exist.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
Full content profile for one brand: description, taglines, hashtags, CTA/website URL, niche (category/subcategory), content type, target platforms, and active discount. Use this to write on-brand captions BEFORE calling create_draft or schedule_post. Read-only; returns no secrets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | yes | — |
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
List posts across all platforms, newest scheduled first. Each row is one publication on one platform. Filter by status (draft|scheduled|posting|posted|failed|cancelled) and/or platform (youtube|tiktok|instagram|...). Returns caption, brand name, permalink, error message when present, and publishWarning for posts that succeeded with an anomaly (e.g. published without media).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| platform | string | no | Filter to a single platform, e.g. youtube or tiktok |
| limit | integer | no | — |
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
High-level snapshot of the posting pipeline: active brand count, a status breakdown (how many scheduled/posted/failed/etc.), a per-platform breakdown, how many posts are due in the next 7 days, and the next scheduled date. Use for 'how's the pipeline?' style questions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
List connected platform accounts (channels) and their health: platform, account username, connected flag, posting-enabled flag, and token expiry. Use to check which platforms are wired up and whether any connection has expired. Never returns access or refresh tokens.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
Publish-outcome metrics over a rolling window (default 30 days): posted/failed/cancelled totals, success rate, per-platform breakdown, and the most recent published posts with permalinks plus their latest stored engagement snapshot (views/likes/comments/shares; available for youtube/tiktok/twitter/threads). Snapshots are stored, not live: call refresh_post_metrics first if the numbers must be curr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | — |
| platform | string | no | — |
| days | integer | no | — |
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
The forward content pipeline: drafts awaiting approval first, then scheduled posts in publish order. Use to review what is queued before it goes out, and to find draft ids for schedule_post.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
Per-brand campaign rollup (brands are ViralCat's campaign unit): posted/scheduled/failed/draft counts, platforms used, next scheduled date, last posted date, and auto-post settings. Optionally scope to one brand_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | — |
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
Group failed posts by platform + normalized failure reason: counts, date range, affected brands, a sample raw error, a recoverable flag (retry_failed_posts can re-queue it) and a concrete suggested fix per group. Answers "what is broken and why" in one call. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Rolling window of failed posts to analyze |
| platform | string | no | Scope to a single platform, e.g. pinterest |
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
READ-ONLY: validate a post BEFORE it is scheduled or published, so a problem is caught up front instead of discovered as a failure afterwards. Checks the exact things that produced the failed-post backlog: incompatible media for the platform (e.g. video to Pinterest), a disconnected or unrefreshable platform token (LinkedIn has no refresh token on this API tier and needs a manual browser reconnect
| Parameter | Type | Required | Notes |
|---|---|---|---|
| post_id | integer | no | Check one existing post (id from list_posts or content_queue). Omit to scan the whole upcoming queue instead. |
| limit | integer | no | Queue-scan mode only: how many upcoming posts to check. |
| include_samples | boolean | no | Include sample users (email contains "sample"). Default: real data only. |
WRITE (safe): create a DRAFT post for a brand. Drafts are never picked up by the publisher, so nothing goes live; a human approves in the dashboard or promotes it later with schedule_post. scheduled_date is a proposed slot (default: 7 days out).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | yes | — |
| platform | string | yes | Target platform, e.g. youtube, tiktok, instagram |
| caption | string | no | Post body. Omit to inherit the brand's taglines. |
| scheduled_date | string | no | Proposed ISO 8601 slot, e.g. 2026-07-15T09:00:00Z |
| skip_hashtags | boolean | no | true = publish the caption as-is with NO brand hashtags appended; false = always append them. Omit to auto-detect: long hand-authored captions (>280 chars, no '#') skip hashtags. The result's hashtags |
| reply_text | string | no | Follow-up reply posted under the main post. On X this is where a link belongs: a URL in the post body costs up to 94% of the reach (near-total on a non-Premium account), while the same URL one reply d |
WRITE (gated): queue a post for FUTURE publishing, at least 15 minutes out (immediate posting is not available over MCP). Either pass post_id to promote an existing draft, or brand_id + platform to create a new scheduled post. The publishing cron sends it at the scheduled time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| post_id | integer | no | Draft post id to promote (from content_queue) |
| brand_id | string | no | — |
| platform | string | no | — |
| caption | string | no | — |
| scheduled_date | string | yes | ISO 8601, at least 15 minutes in the future |
| skip_hashtags | boolean | no | true = publish the caption as-is with NO brand hashtags appended; false = always append them. Omit to auto-detect: long hand-authored captions (>280 chars, no '#') skip hashtags. When promoting a draf |
| reply_text | string | no | Follow-up reply posted under the main post. On X this is where a link belongs: a URL in the post body costs up to 94% of the reach (near-total on a non-Premium account), while the same URL one reply d |
WRITE (safe): cancel a queued post, or move it to a new slot. Omit scheduled_date to CANCEL (status -> cancelled; the publisher ignores it). Pass scheduled_date to RESCHEDULE to that time instead (ISO 8601, at least 15 minutes out; a draft keeps its draft status). Works on draft or scheduled posts (cancel or reschedule); also works on FAILED posts but cancel-only (omit scheduled_date) — this is th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| post_id | integer | yes | Post id to cancel or reschedule (from content_queue) |
| scheduled_date | string | no | Omit to cancel. Provide to reschedule: ISO 8601, at least 15 minutes in the future |
WRITE (gated): bulk re-queue recoverable failed posts (default reason classes: token_expired, missed_window, platform_transient_error, drive_media_missing). dry_run DEFAULTS TO TRUE and only returns the plan; pass dry_run=false to actually reschedule. Retries are staggered per platform (spacing_minutes apart) and capped at limit, so a bulk retry cannot dogpile a platform API. Posts that would stru
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dry_run | boolean | no | true = plan only, change nothing (the default) |
| platform | string | no | Scope to a single platform |
| reasons | array | no | Failure reason classes to retry. Default: token_expired, missed_window, platform_transient_error, drive_media_missing. Non-retryable classes are rejected. |
| limit | integer | no | — |
| start_at | string | no | ISO 8601 start of the retry window, at least 15 minutes out. Default: ~20 minutes from now. |
| spacing_minutes | integer | no | Gap between retries on the same platform |
WRITE (gated): move ONE post to a new future slot (ISO 8601, at least 15 minutes out). Unlike cancel_post this also accepts FAILED posts: a failed post is re-queued (status -> scheduled, error cleared). Draft and scheduled posts keep their status. Refuses posts that would structurally fail again (archived brand, incompatible media, Facebook with no Page).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| post_id | integer | yes | Post id (from list_posts, content_queue or diagnose_failures) |
| scheduled_date | string | yes | New slot, ISO 8601, at least 15 minutes in the future |
WRITE (gated): fetch current engagement (views/likes/comments/shares) for already-published posts and store today's snapshot, then read it back with post_performance. This is the only way to update the numbers without opening the dashboard Stats tab. Supported platforms: youtube, tiktok, twitter, threads; LinkedIn and the rest expose no engagement API. A 60-minute cooldown applies per account and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_samples | boolean | no | Include sample users. Default false: real accounts only, matching every read tool. |
WRITE (safe): attempt a server-side token refresh for a platform whose access token has lapsed, updating the stored connection's token/expiry. Works without a browser when a refresh token is on file (twitter/youtube/google_drive self-heal this way); returns needsManualReauth + a dashboard link when the platform genuinely requires a manual browser reconnect (e.g. threads). Cannot publish or touch c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | yes | Platform to reconnect, e.g. twitter, youtube, google_drive |
WRITE (gated): fetch a public media URL and store it in the connected Google Drive, returning the Drive fileId to pass to create_draft or schedule_post. This uploads to YOUR OWN Drive; it publishes nothing and reaches no audience. Accepts video, image or audio up to 100MB. With brand, files land in the folder the generator actually reads for that media type: Viral-Cat/_Res/{brand}/Imgs for an imag
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_url | string | yes | Public https URL of the media to store, e.g. a rendered Short. Must be reachable without auth. |
| file_name | string | no | Name to save as. Omit to take it from the URL. |
| brand | string | no | Brand whose _Res/{brand} folder should receive the file. Ignored when folder_id is given. |
| kind | string | no | Which brand folder receives the file: Vids, Imgs or Music. Omit to route by media type, which is almost always right. |
| folder_id | string | no | Destination Drive folder id, overriding brand. Omit to use the Viral-Cat folder. |
WRITE (gated): open a Google Drive upload session for media you hold locally, so a clip rendered on your own machine never has to be published publicly just so ViralCat can fetch it back. Returns an uploadUrl - PUT the bytes to it yourself (no auth header) and Drive stores the file; the response Location/id is the fileId for create_draft or schedule_post. When brand is given the file lands in the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_name | string | yes | Name to save as in Drive, e.g. "ducktax-short.mp4". |
| mime_type | string | yes | Media type of the file, e.g. "video/mp4". |
| size_bytes | integer | yes | Exact byte length of the file. Drive rejects a mismatch. |
| brand | string | no | Brand whose _Res/{brand} folder should receive the file. Ignored when folder_id is given. |
| kind | string | no | Which brand folder receives the file: Vids, Imgs or Music. Omit to route by media type, which is almost always right. |
| folder_id | string | no | Destination Drive folder id, overriding brand. |
WRITE (gated): create a brand (content profile) so create_draft and schedule_post have something to target. Every other write here needs a brand_id, so an agent had no way to set one up. Returns the brand_id and the Drive folder the publisher will read its media from (Viral-Cat/_Res/{name}/Vids). Publishes nothing and reaches no audience.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Brand name. Also names its Drive media folder, so keep it filesystem-friendly. |
| description | string | no | — |
| hashtags | array | no | Brand hashtags appended to captions unless skip_hashtags is set. |
| cta_url | string | no | Link included in posts. |
| website_url | string | no | — |
| content_type | string | no | What the publisher should expect to find for this brand. |
WRITE (gated): correct a brand's content profile: description, taglines, hashtags, CTA and website links, content type, and the auto-post switch. This is the repair path for a brand carrying wrong copy, which otherwise makes every caption for it wrong, and the off switch for a brand whose generator is posting against your content rules. Only the fields you pass change; the rest keep their stored v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | yes | — |
| description | string | no | What the product actually is. The generator writes captions from this, so a wrong description makes every post wrong. |
| taglines | array | no | Short lines the publisher rotates through when a post has no caption of its own. |
| hashtags | array | no | Brand hashtags appended to captions unless skip_hashtags is set. |
| cta_url | string | no | Link included in posts. Pass an empty string to clear it. |
| website_url | string | no | — |
| content_type | string | no | What the publisher should expect to find for this brand. |
| auto_post_enabled | boolean | no | false = stop the content generator booking posts for this brand from its next cycle; true = let it resume. This is the only way to stop a brand auto-posting without opening the dashboard. Already-sche |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ViralCat or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ViralCat can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.