Turn raw URLs into viral hits. Because manually writing posts is so 2025.
ViralTransformer is a high-performance MCP server that turns Claude into a 24/7 social media growth hacker. It doesn't just scrape; it thinks, analyzes, and drafts.
Feature | Description |
The "Remake" Command | Give Claude a URL and say "remake this"One-click rewriting: Feed Claude a link and get both deep business insights and high-engagement viral posts |
Dual-Version Output | Get "Deep Insight" for LinkedIn and "High-Energy" for X/SocialDual output: Simultaneously generate deep LinkedIn observations and high-energy viral posts for X/Xiaohongshu |
Local Drafts | Auto-saves every genius idea to |
Related MCP server: MCP Google Maps
Every ā unlocks a new creative capability.
Stars | Achievement |
ā50 | The Roast Master ā AI rewrites news with extreme sarcasm |
ā188 | Cyberpunk 2077 ā Tech-noir storytelling: Rewrite mundane tech updates with neon, cybernetic, and dystopian flair. |
ā300 | The Abstract Master ā Post-modern "Madness" style: Unlock "Internet Abstract" language, nonsense literature, and chaotic styles. |
ā520 | "Blind Date" Profile ā News as a high-end date bio: Rewrite dry financial reports into "high-net-worth, elite, skiing-loving" socialite dating profiles. |
ā888 | "The Secret Agent" ā Auto-monitor competitors: Automated tutorials for monitoring competitor activity and generating "counter-attack" copy. |
FastMCP: High-performance Python framework for MCP.
Httpx: Async-first engine for rapid content retrieval.
BeautifulSoup4: Robust HTML parsing.
Pydantic: Ensuring strict type safety and structured data outputs.
Python 3.10+
uv (Recommended for dependency management)
# Clone the repository
git clone https://github.com/BelleKou/mcp-viral-transformer.git
cd mcp-viral-transformer
# Install dependencies (Modern way)
uv pip install -e .
# Or the traditional way
pip install -r requirements.txtTo use this server, you need an Anthropic API Key. Set it in your environment:
ANTHROPIC_API_KEY: Your key from the Anthropic console.
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"viral-transformer": {
"command": "uv",
"args": [
"run",
"--with", "mcp",
"mcp", "run",
"/your/path/to/mcp-viral-transformer/server.py"
]
}
}
}ā ļø Replace the path with your actual local path.
Source: Anthropic's $30B Compute Deal
Generated File: š drafts/anthropic_30b.md
ā”ļø THE $30B COMPUTE HEGEMONY: ANTHROPIC X GOOGLE X BROADCOM
šļø Version A: Professional Insight
Title: The Death of Asset-Light AI: Anthropic's Vertical Integration Bet
The recent $30B partnership between Anthropic, Google, and Broadcom marks a tectonic shift. We are moving away from "Algorithm Supremacy" toward "Compute Sovereignty."
The Hardware Pivot: Co-designing ASICs with Broadcom to bypass the NVIDIA bottleneck.
Infrastructure Moat: Scaling laws now require a direct relationship with the power grid.
š Version B: High-Energy Viral
Title: $30 BILLION. That's the price of admission for the AGI race. šø
While everyone is arguing over prompts, Anthropic just bought the building. And the chips. And the power lines.
š® UNIQUE ANGLE
AI is shifting from software to a "Digital Utility." In 2026, the leading AI company looks less like Microsoft and more like a combination of TSMC and energy conglomerates.
Source: 36Kr - Geely Aerofugia IPO
Generated File: š drafts/sky_economy.md
š 11 IPOs! The final piece of the "Car Maniac's" puzzle: The low-altitude economy isn't a dream, it's a business.
šļø Version A: Deep Business Insight
Title: From "2D Roads" to "3D Space": Aerofugia's Capital Strategy
Aerofugia's IPO counseling marks the entry of the "low-altitude economy" from concept to capital harvest. This is not just about building flying cars, but about reconstructing urban spatial sovereignty.
š Version B: High-Energy Viral
Title: Stop grinding on the ground! Need a "flying taxi" in 10 minutes? šø
The "crazy talk" mocked back then has all come true! The sky is officially becoming a "lane," and the era of low-altitude travel is here. They aren't selling planes; they're selling the "privilege to bypass traffic."
š® UNIQUE ANGLE
Class stratification of temporal sovereignty: In 2026, class division will be reflected in "vertical access rights." The 300-meter altitude captured by Aerofugia is the ultimate interpretation of urban order for the next 50 years.
.
āāā server.py # Core MCP logic
āāā LICENSE # MIT License
āāā requirements.txt # Project dependencies
āāā drafts/ # Generated markdown posts (Output)
āāā README.md # DocumentationLicensed under the MIT License. Open for modification and personal use.
Saves content with a safe filename to the /drafts folder.
| Name | Required | Description | Default |
|---|---|---|---|
| filename | Yes | ||
| content | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'saves content' (implying a write operation) and mentions a 'safe filename', but doesn't clarify permissions, error handling, or what 'safe' entails. This leaves significant gaps for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's action and destination. It's front-loaded with the core purpose and has no wasted words, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema (which reduces the need to describe return values) but no annotations and 0% schema coverage, the description is minimally adequate. It covers the basic action and location but lacks details on behavior and parameters, making it incomplete for a mutation tool with undocumented inputs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It mentions 'safe filename' and '/drafts folder', which adds some context for the 'filename' parameter, but doesn't explain 'content' or provide details on filename safety rules. This partial compensation is insufficient for the 2 undocumented parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Saves content') and target ('to the /drafts folder'), with the verb 'saves' being specific. However, it doesn't differentiate from the sibling tool 'scrape_article' (which appears unrelated), so it doesn't fully earn a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It mentions saving to '/drafts folder' but doesn't specify use cases, prerequisites, or exclusions, leaving the agent with minimal context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Scrapes clean content from a URL, focusing on the main article body.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool scrapes clean content and focuses on the main article body, which hints at behavior like content cleaning and body extraction. However, it lacks details on error handling, rate limits, authentication needs, or what 'clean' entails, leaving significant gaps for a tool with no annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core action and focus. Every word earns its place, with no redundancy or unnecessary elaboration, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema (which covers return values), no annotations, and a simple input schema, the description is minimally adequate. It specifies the tool's focus on article body content, but for a scraping tool with no behavioral annotations, it could benefit from more context on limitations or expected output format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not mention the 'url' parameter explicitly, but with only 1 parameter and 0% schema description coverage, it compensates by implying the parameter's purpose through context ('from a URL'). This adds meaning beyond the bare schema, though it doesn't detail format or constraints, keeping it from a perfect score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('scrapes') and resource ('clean content from a URL'), specifying it focuses on the main article body. This distinguishes it from generic scraping tools, though it doesn't explicitly differentiate from the sibling 'save_draft' tool, which appears unrelated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, such as other scraping methods or tools. It mentions focusing on the main article body, which implies a context for article content extraction, but lacks explicit when/when-not instructions or named alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The two tools have completely distinct purposes: save_draft handles local file saving with safe naming, while scrape_article extracts clean content from URLs. There is no overlap in functionality or ambiguity between them.
Both tools follow a consistent verb_noun pattern (save_draft, scrape_article) with clear, descriptive names that align well with their functions. The naming style is uniform and predictable.
With only two tools, the server feels thin and under-scoped for a 'ViralTransformer' purpose, which implies content transformation or viral content handling. This minimal set limits functionality and suggests incomplete coverage of the domain.
The tool set is severely incomplete for a viral content transformation server. It lacks core operations like content generation, editing, publishing, analytics, or social media integration, leaving significant gaps that will hinder agent workflows.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for QPost ā lets AI agents publish video and image posts to YouTube, TikTok, Instagram.
WordPress MCP server: generate SEO posts, AI images, autoblog & WooCommerce on your self-hosted site
Connect any AI agent to 11+ social platforms: schedule, publish & track posts via hosted MCP.
MCP server for Google Veo AI video generation
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BelleKou/mcp-viral-transformer'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
