Publish MCP content factory for Telegram, VK and MAX

publish-mcp

An MCP server generates, translates and publishes posts to Telegram, VK, MAX and Threads: brand profile, competitor analysis and images in one pipeline

MCP server

High risk

We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.

Why this level

  • Publishes posts across several messengers on behalf of the token owner
  • Sends content to an external AI provider for text and image generation
All reasons and checks
Russian stack

devladpopov/publish-mcp

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/publish-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio --env 'GEMINI_API_KEY=<your GEMINI_API_KEY>' publish -- npx -y content-factory-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "publish": {
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "publish": {
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"publish","type":"stdio","command":"npx","args":["-y","content-factory-mcp"],"env":{"GEMINI_API_KEY":"<your GEMINI_API_KEY>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "publish": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add publish --env 'GEMINI_API_KEY=<your GEMINI_API_KEY>' -- npx -y content-factory-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.publish]
command = "npx"
args = ["-y", "content-factory-mcp"]
env = { GEMINI_API_KEY = "<your GEMINI_API_KEY>" }

If the file already exists, append the block to the end.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "publish": {
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "publish": {
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "publish": {
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "publish": {
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "publish": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "content-factory-mcp"
      ],
      "environment": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "publish": {
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "publish": {
      "command": "npx",
      "args": [
        "-y",
        "content-factory-mcp"
      ],
      "env": {
        "GEMINI_API_KEY": "<your GEMINI_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

TELEGRAM_BOT_TOKENsecret, optional
TELEGRAM_CHAT_IDoptional
GEMINI_API_KEYsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 4c53568.

Text for your agent

Add npx -y content-factory-mcp to your MCP client config with TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID and GEMINI_API_KEY environment variables, then call setup_brand before the first post generation.

Other ways from the author
{
  "mcpServers": {
    "publish": {
      "command": "npx",
      "args": ["-y", "content-factory-mcp"],
      "env": {
        "TELEGRAM_BOT_TOKEN": "123456:ABC-DEF...",
        "TELEGRAM_CHAT_ID": "@my_channel",
        "GEMINI_API_KEY": "AIza..."
      }
    }
  }
}

The README's quick start; VK and MAX are wired in via additional env vars per the server's docs.

This is third-party code. Review the repository files before installing.

What it does

The server gives 11 tools covering the full content cycle: setup_brand sets a niche, tone and post structure, analyze_competitors scrapes and AI-analyzes competitor pages, find_sources discovers RSS feeds and sites for a niche, generate_post writes a post in the brand voice, translate_post translates while keeping the style, and generate_media creates an image via Gemini Imagen or DALL-E. Publishing is separate: publish sends text and an optional image to one channel, publish_all sends to every configured channel at once, list_channels shows what is configured, and preview does a dry run without a real send. The README states it is already used for channels totaling over 157,000 subscribers.

Who it is for. For people running content across several messengers who want ready-made posts from a single agent request.

Good fit when

  • You want the full cycle from topic to publishing in Telegram, VK, MAX and Threads in one server
  • You need competitor analysis before writing a post
  • You need a finished post translated to another language while keeping the brand voice

Not a fit when

  • You want publishing without an external AI provider, text and image generation depend on Gemini or compatible keys
  • You only need posting without content generation, a specialized single-platform server would be simpler

Example request

Set up my brand for the AI education niche, find sources, write a post about the new model and publish to all channels

Limitations

Text and image generation depends on an external key (GEMINI_API_KEY in the README's example), meaning it needs an accessible foreign provider. No license is stated in the repository. The README does not detail VK and MAX publishing rate limits.

How to disable. Remove the publish server from your MCP client configuration and revoke the Telegram, VK and MAX tokens in their respective consoles.

MCP

Transport
stdio
Authentication
API key
Environment variables
Environment variables
TELEGRAM_BOT_TOKEN
secret
The Telegram bot token for publishing to a channel.
TELEGRAM_CHAT_ID
The Telegram channel's id or username.
GEMINI_API_KEY
required, secret
A Gemini key for text and image generation.

Security check

  • Publishes posts across several messengers on behalf of the token owner
  • Sends content to an external AI provider for text and image generation

README in short

The English README presents the server as an AI content factory for Telegram, VK, MAX and Threads through a single MCP config. It gives a table of 11 tools split into a content-factory block (brand, competitors, sources, text generation, translation, images) and a publishing block (single, bulk, channel listing, preview). It shows a full pipeline example from setting up a brand to publishing and states the subscriber count of channels already using it.

FAQ

Can I preview a post before publishing?

Yes, the preview tool does a dry run without a real send to the channel.

Does the server support MAX?

Yes, the README lists MAX among the publishing platforms alongside Telegram, VK and Threads.

Editors’ pick

A skill that strips AI writing tells from text using Wikipedia's list, without adding invented facts

SkillLow riskNo VPN needed52.7KRepository stars

Marketing Skills for AI agents

Marketing Skills for AI Agents

Editors’ pick

About fifty skills for CRO, copywriting, SEO, analytics, ads and launches, built for coding agents

SkillLow risk51.8KRepository stars
Official

SendPulse's official remote MCP server: statistics, campaigns and user data through an agent chat

MCP serverHigh riskRussian stack1Repository stars
Editors’ pick

An MCP server and CLI covering all 113 Yandex Direct API v5 methods generated from WSDL, exposing 9 read tools by default and writes only on demand

MCP serverHigh riskRussian stackNo VPN needed1Repository stars
Foxx AIPublish MCP content factory for Telegram, VK and MAX

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.