MCP and plugin for Retensy bot funnels
retensy-mcp
Retensy's official MCP server and skill for building and publishing Telegram, MAX and Instagram bot funnels from a text description
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
- The token grants full Retensy account access, including publishing and deleting scenarios
- Scenarios can pass leads to connected CRMs and publish live changes to real bots
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/retensy-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run one by one in the Claude Code chat
/plugin marketplace add retensy/retensy-mcp
/plugin install retensy-mcp@retensyInstall the plugin with /plugin marketplace add retensy/retensy-mcp and /plugin install retensy-mcp@retensy in Claude Code, then create a token at bots.retensy.com/bots/mcp-tokens and send it to the agent, which saves it with the set_token tool.
Other ways from the author
/plugin marketplace add retensy/retensy-mcp
/plugin install retensy-mcp@retensyThe recommended method, pulls in both the MCP server and the skill.
This is third-party code. Review the repository files before installing.
What it does
The server gives 30-plus tools for building and publishing bots in the Retensy /bots service: listing bots, graphs, channels and connected integrations (amoCRM, Bitrix24, GetCourse, Yandex Metrika, with their connectionId for scenario actions), creating and editing a graph, live-editing an active graph with auto-backup, targeted JSON replacements on the server, a dry run without publishing, templates and graph cloning, media uploads up to 50 MB, funnel-path analytics by node, and a list of subscribers and UTM tracking links. The build-bot-funnel skill assembles a node-and-edge graph for Telegram, MAX and Instagram and checks it with a local validator before uploading. On a tool failure, the server sends an anonymous report to its own server (tool name, error category, no tokens or graph content), which can be turned off or switched to full telemetry for debugging your own install.
Who it is for. For Retensy teams whose bots are already tied to CRM and course platforms and who want to build funnels in words instead of a visual editor.
Good fit when
- You want to describe a bot funnel in words and publish it straight to Retensy /bots
- The scenario needs to pass a lead to amoCRM, Bitrix24, GetCourse or send a goal to Yandex Metrika
- You need analytics on which funnel node subscribers drop off at
Not a fit when
- You do not have a Retensy account: the tools only work with its API
- You need broadcasts or a SUBSCRIBED condition in a MAX bot: the platform does not support them in this service
- You do not want anonymous error telemetry sent: set RETENSY_MCP_TELEMETRY=off from the start
Example request
Build a bot: a greeting start, a three-button question, and pass the lead to amoCRM; upload and publish itLimitations
The token grants full Retensy account access, equivalent to logging into the dashboard. MAX lacks the SUBSCRIBED condition and reply keyboards, Instagram has no broadcasts, and its delay is capped at 24 hours. By default, a tool failure sends an anonymous report to Retensy's server with the tool name, failure category and package version, with no tokens or graph content.
How to disable. Revoke the token on the /bots/mcp-tokens page in Retensy, or remove the retensy-mcp server from your MCP client config.
Security check
- The token grants full Retensy account access, including publishing and deleting scenarios
- Scenarios can pass leads to connected CRMs and publish live changes to real bots
README in short
The README closely mirrors the structure of the sibling zaytsv-mcp project (the same 30-plus tool set, the same graph format and validator), but adds a list_integrations tool for amoCRM, Bitrix24, GetCourse and Yandex Metrika, and a dedicated section on anonymous error reports: what is sent, what is never sent, and three environment variables for controlling telemetry.
FAQ
Can a scenario be tied to amoCRM or Bitrix24?
Yes, the list_integrations tool shows connected services and their connectionId for use in scenario actions.
Is my data sent on an error?
Only an anonymous technical report with no tokens, passwords or graph content is sent, and telemetry can be turned off with RETENSY_MCP_TELEMETRY=off.
Related
An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n
Zapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account
Awesome Claude Skills by Composio
Awesome Claude Skills
A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps
A plugin and CLI catalog for agents: generates command-line interfaces for GUI apps like GIMP and Blender and installs ready ones via CLI-Hub