FlowCastle vs Tgcloud — Telegram serverless bots
A side-by-side look at the FlowCastle and Tgcloud — Telegram serverless bots 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 FlowCastle for communication work over a hosted endpoint; choose Tgcloud — Telegram serverless bots for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tgcloud — Telegram serverless bots | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 39/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | FLOWCASTLE_MCP_TOKEN | TGCLOUD_CLITGCLOUD_CLI_ARGSTGCLOUD_TIMEOUT_MS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View FlowCastle | View Tgcloud — Telegram serverless bots |
Tools & capabilities
FlowCastle tools
No tool names declared yet. Check the project README from the listing page.
Tgcloud — Telegram serverless bots 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.
FlowCastle
{
"mcpServers": {
"flowcastle": {
"url": "https://api.flowcastle.ai/api/mcp"
}
}
}
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"
}
}
}
}
Frequently asked questions
FlowCastle is categorized under Communication and uses a remote HTTP/SSE transport. Tgcloud — Telegram serverless bots belongs to Communication and uses a local stdio subprocess. Pick FlowCastle for communication work and Tgcloud — Telegram serverless bots 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.
FlowCastle has no declared pricing — check the project's own site. Tgcloud — Telegram serverless bots is listed as free. 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 flowcastle and tgcloud-telegram-serverless-bots as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FlowCastle has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 2 GitHub stars. Tgcloud — Telegram serverless bots has 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.