MCP autoposting for Telegram, VK and TenChat

Customer MCP Autoposting

An MCP server publishes one text at once to Telegram, VKontakte (group and personal wall) and TenChat with a single publish_all call

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • Publishes to a VK wall, a VK group and Telegram on behalf of the token owner
  • Stores the TenChat browser session locally
All reasons and checks
Russian stack

PavelKarikoff/Customer_MCP_Autoposting

Install

Services

Manual install

git clone https://github.com/PavelKoff2025/Customer_MCP_Autoposting.git && cd Customer_MCP_Autoposting/mcp-social-autopost && npm install && cp .env.example .env && npm run build

Install and build from the README; npm run tenchat:login for TenChat follows.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Publishes to a VK wall, a VK group and Telegram on behalf of the token owner
  • Stores the TenChat browser session locally

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

What it does

The server solves a solo marketer's problem: not copy-pasting a post into three tabs by hand. The create_post tool prepares content, publish_all sends it to every configured platform at once: Telegram via the Bot API, VKontakte via the VK API to both a group and a personal wall simultaneously, and TenChat via Playwright with a saved browser session, since TenChat has no public API. Publishing is idempotent: state is kept in storage/state, so a repeat call does not duplicate already published posts. There is a dry_run for testing before a real send, cover generation via a configurable IMAGE_API_URL, and separate post_status and list_platforms tools.

Who it is for. For marketers and solopreneurs running content simultaneously across Telegram, VK and TenChat who want to publish in one action.

Good fit when

  • You want to publish the same post to Telegram, VK and TenChat without manual copying
  • You want to test a publish with dry_run before actually sending
  • You want to know where a post was already published to avoid duplicates

Not a fit when

  • You need platforms other than Telegram, VK and TenChat, the list is hard-limited to three
  • You do not want to log into TenChat via a saved Playwright browser session

Example request

Publish a post about the new feature to all platforms, show a dry-run first

MCP

Transport
stdio
Authentication
API key

Environment variables

IMAGE_API_URL
The address of the cover image generation service for posts.

Limitations

The repository license is marked private. TenChat needs a one-time login via npm run tenchat:login, since the platform has no public API, and the browser session is saved locally. Cover generation needs a separate IMAGE_API_URL, not bundled with the server itself.

How to disable. Remove the social-autopost server from .claude/mcp.json and delete the storage/state folder with saved sessions.

FAQ

Can a repeat call duplicate posts?

No, the server keeps publish state in storage/state and does not send again where it already published.

How does it publish to TenChat without an API?

Through Playwright and a saved browser session after a one-time login with npm run tenchat:login.

Discussion

No questions or reviews yet.

Russian stack

A compact VK community MCP server: post publishing with scheduling, photo uploads, statistics and comments

MCP serverBroad access
Russian stack

An MCP server for the VKontakte wall: reading and posting, messages, friends, communities and group stats in 8 tools

MCP serverBroad access1Repository stars
Russian stack

A 4-tool MCP server that pulls VK wall posts, filters them by rules and publishes them to Telegram via the Bot API

MCP serverBroad access

24Repost MCP

24repost-mcp

Official

Remote MCP server of 24Repost: an agent creates post forwarding routes between Telegram, MAX and VK and sets the copy rules

MCP serverBroad access
Russian stack

Remote MCP server for VK communities: 50 tools, posts, comments, dialogs, photos, video and products, with writing off by default

MCP serverBroad access

README in short

The Russian README states the goal plainly: one MCP server, posts to Telegram, VKontakte and TenChat at once, no copy-pasting and no manual tabs. A platform table shows how each one publishes and its quirks, including two targets at once for VK. It lists the MCP tools and resources, shows a quick start with npm install, a build step and a separate TenChat login, and a ready .claude/mcp.json file for Claude Code and Cursor.

README badge

Report a problem