SkillFoxx

BotHelp scenario MCP plugin

bothelp-mcp

An MCP server and Claude Code plugin that reads and edits BotHelp scenario graphs and broadcasts via the flow2 builder's private WebSocket

  • 0 ★ on the repository
  • Last commit
  • MIT
Plugin

Broad access

Why this level

  • Edits a bot's live scenario graph: blocks, transitions, layout
  • Creates, repeats and cancels broadcasts to subscribers
  • Uses a captured operator session through a private, undocumented protocol
All reasons and checks
Russian stack

skiddgoddamn/bothelp-mcpAuthor:skiddgoddamn

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/bothelp-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

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

  • Edits a bot's live scenario graph: blocks, transitions, layout
  • Creates, repeats and cancels broadcasts to subscribers
  • Uses a captured operator session through a private, undocumented protocol

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

What it does

The server exposes 25 tools on top of two BotHelp capabilities the public Open API does not offer: editing the scenario graph (blocks, transitions, canvas layout) and managing broadcasts (create, repeat with new text or buttons, cancel, delete, draft or send now). BotHelp's public Open API only reads and runs scenarios; only the flow2 web builder can edit the graph, through a private, undocumented WebSocket RPC built on the Primus library, and this server is a thin wrapper over the same methods. Authorization uses an operator session rather than an Open API token: either a direct email and password (the password is never stored, only the resulting sessionId goes into the config), or a ready sessionId captured from DevTools. An escape-hatch call tool lets you call any builder method directly.

Who it is for. For people building and editing BotHelp bot scenarios who want to do it from Claude Code, not only by hand in the web builder.

Good fit when

  • You need to change the scenario graph (blocks, transitions, layout) programmatically
  • You need to schedule, repeat with edits, or cancel a broadcast
  • You have a test bot where changes can be verified safely before production

Not a fit when

  • You want an official stable API rather than a private protocol that can change without notice
  • You only need Open API statistics viewing, the same author has a separate skill for that
  • You are not ready to test changes on a test bot before applying them to a live scenario

Example request

Repeat the last broadcast with broadcastId 42 using new text and replace the utm in links, show a dry-run first

Limitations

The protocol is private, undocumented and unofficial: the author warns it can change without notice and advises testing changes on a test bot, since add_block, delete_block and save_layout modify a live scenario. The README explicitly calls the project an unofficial client not affiliated with BotHelp and advises staying within the service's terms. For a fully official approach with an API token instead of a captured session, the author points to the retensy-mcp alternative.

How to disable. Run /plugin uninstall bothelp-mcp in Claude Code, or remove the bothelp-mcp server from your MCP client configuration.

FAQ

Why not just use the official Open API?

BotHelp's Open API only reads and runs scenarios; editing the graph and managing broadcasts is only possible through the flow2 web builder's private WebSocket RPC, which this server wraps.

Is the password transmitted or stored anywhere?

No, with login_password the password is used once to obtain a sessionId and never enters the config; only the resulting session is saved.

Discussion

No questions or reviews yet.

All VK tools

BotHelp analytics skill

claude-skill-bothelp

Russian stack

A Claude Code skill for the BotHelp Open API: a bot map, step-by-step drop-off, subscriber export and limited management via the open API

SkillExtended access
Russian stack

An MCP server and skill for building and publishing Telegram, MAX and Instagram bot funnels in the zaytsv /bots service from a text description

PluginBroad access1

Telegram API MCP

telegram-api-mcp

Russian stack

MCP server for the Telegram Bot API: messages, channels, forums, payments and long posts from a bot, with Telegram rate limits built in

MCP serverBroad access34
Official

Retensy's official MCP server and skill for building and publishing Telegram, MAX and Instagram bot funnels from a text description

PluginBroad access
Russian stack

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

MCP serverBroad access

Max Bot MCP server

Max Bot MCP Server

Russian stack

An MCP server that reads a bot's messages in the Max messenger: chats, members, text search and attachment downloads

MCP serverExtended access1

README in short

The README explains in detail why the server uses WebSocket rather than the Open API: the public REST API only reads and runs, while only the flow2 builder can edit the graph, through a private Primus protocol. It lists 25 scenario and broadcast tools, two session-based (not token-based) authorization methods, installation as a plugin or a plain MCP server via npx, an escape-hatch call tool for any method, and an explicit unofficial-status warning advising testing on a test bot, with a pointer to the official retensy-mcp alternative.

README badge

Report a problem