tgcloud — Telegram serverless bots MCP Server

What the code does

We read the source, 20 h ago · rules ccca72095570

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const child = spawn(process.execPath, [path.join(root, scripts[cmd]), ...process.argv.slice(3)], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add tgcloud-mcp -- npx -y tgcloud-mcp

{
  "mcpServers": {
    "tgcloud-mcp": {
      "args": [
        "-y",
        "tgcloud-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.tgcloud-mcp]
command = "npx"
args = ["-y", "tgcloud-mcp"]

{
  "mcpServers": {
    "tgcloud-mcp": {
      "args": [
        "-y",
        "tgcloud-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "tgcloud-mcp": {
      "args": [
        "-y",
        "tgcloud-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: TGCLOUD_CLI (Command that launches the tgcloud CLI (default npx; may be a proxy wrapper)), TGCLOUD_CLI_ARGS (Arguments placed before the subcommand (default 'tgcloud')), TGCLOUD_TIMEOUT_MS (Timeout of one CLI command, in milliseconds), TGCLOUD_TOKEN (CLI access token from @BotFather (form app<id>:<secret>), used instead of tgcloud login). The author declared them in the registry entry; get the values from the project itself.