Tgcloud — Telegram serverless bots vs FlowCastle
A side-by-side look at the Tgcloud — Telegram serverless bots and FlowCastle MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
Tgcloud — Telegram serverless botsCommunication · Local subprocess (stdio)MCP server for Telegram serverless bots: lifecycle, deploys, migrations, webhooks via tgcloud CLI40FairAuth: not declaredVerdict: choose Tgcloud — Telegram serverless bots for communication work as a local process; choose FlowCastle for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
TChoose Tgcloud — Telegram serverless bots when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TGCLOUD_CLI, TGCLOUD_CLI_ARGS, TGCLOUD_TIMEOUT_MS.
Choose FlowCastle when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
FLOWCASTLE_MCP_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tgcloud — Telegram serverless bots | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 40/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | TGCLOUD_CLITGCLOUD_CLI_ARGSTGCLOUD_TIMEOUT_MS | FLOWCASTLE_MCP_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Tgcloud — Telegram serverless bots | View FlowCastle |
Tools & capabilities
Tgcloud — Telegram serverless bots tools
No tool names declared yet. Check the project README from the listing page.
FlowCastle tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Tgcloud — Telegram serverless bots
{
"mcpServers": {
"tgcloud-telegram-serverless-bots": {
"command": "npx",
"args": [
"-y",
"tgcloud-mcp"
],
"env": {
"TGCLOUD_CLI": "YOUR_TGCLOUD_CLI_HERE",
"TGCLOUD_CLI_ARGS": "YOUR_TGCLOUD_CLI_ARGS_HERE",
"TGCLOUD_TIMEOUT_MS": "YOUR_TGCLOUD_TIMEOUT_MS_HERE"
}
}
}
}
FlowCastle
{
"mcpServers": {
"flowcastle": {
"url": "https://api.flowcastle.ai/api/mcp"
}
}
}
Frequently asked questions
Tgcloud — Telegram serverless bots is categorized under Communication and uses a local stdio subprocess. FlowCastle belongs to Communication and uses a remote HTTP/SSE transport. Pick Tgcloud — Telegram serverless bots for communication work and FlowCastle for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Tgcloud — Telegram serverless bots is listed as free. FlowCastle has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add tgcloud-telegram-serverless-bots and flowcastle as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tgcloud — Telegram serverless bots has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. FlowCastle has 39/100 (Fair) with 1 views, 0 installs and 2 GitHub stars.