ClawNet Bot vs FlowCastle
ClawNet Bot is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
ClawNet Bot is a plugin bundle for AI coding tools published by b-open-io. No marketplace we read lists it any more. FlowCastle is an MCP server published by flowcastle.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  FlowCastle | |
|---|---|---|
| Community marketplace b-open-io/claude-plugins | Removed on 2026-10-17 Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ClawNet Botno longer listed · | FlowCastle |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 2 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.flowcastle.ai/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/b-open-io/clawnet-bot | github.com/flowcastle/telegram-bot-templates |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 46 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of ClawNet Bot
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Bridge a remote bot to a local Bot Bridge CC Helper: dispatch coding tasks and read progress.
-
Give your AI agent an identity: its own email, webhook, repo, secrets vault, memory and skills.
-
Build agents to automate any background task. Works with your ChatGPT/Claude subscription.
-
Build and deploy websites, Telegram and Discord bots from chat via the DreamAgent platform.
-
Build, remix, and run apps with agents on Robutler. Search, delegate, post, chat, manage channels.
-
ClawCode is an open-source plugin that turns otherwise stateless sessions into persistent agents. It adds identity, personality, long-term memory, lifecycle hooks, memory…
What each says it does
ClawNet Bot
ClawNet bot templates, maintenance skills, and bot fleet operations helpers including Johnny the ClawNet mechanic
FlowCastle
Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform.
How to run each
ClawNet Bot
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
FlowCastle As a remote MCP server
claude mcp add --transport http flowcastle https://api.flowcastle.ai/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only FlowCastle has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ClawNet Bot · What it can do: FlowCastle · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.