"Telegram login" matching MCP servers:

Enables remote execution of Codex CLI commands and provides an MCP tool for AI agents to escalate questions to humans via Telegram, allowing for human-in-the-loop workflows when away from the machine.

Gives Amazon Quick Desktop real shell access outside its sandbox, running commands as your own user with login-shell environment, synchronous execution, background jobs, process-tree cleanup on timeout, and an audit log. A narrow pattern-based guard blocks a handful of destructive commands while ordinary work — including targeted recursive deletes — passes through.

Enables AI agents to interact with physical embedded target boards over a dual-CDC USB bridge using MCP tools. It exposes console reading, pattern waiting, command sending, reboot/login state machines, and in-RAM MicroPython execution while a single-owner daemon safely arbitrates access to the serial devices.

MTProto Telegram client for the terminal (Rust): a CLI for messages, media and contacts, an MCP server that pushes server-to-client notifications when new messages land (per-chat filtering), and an SSE stream. Local-first, no third-party APIs, single binary, MIT.

Enables AI agents on Windows to read, write, copy, move, and delete files inside WSL distributions, run shell commands in a login shell, and convert between Windows and Linux path styles. Commands are piped to bash -s via stdin so quotes, $, backticks, and other special characters pass through without Windows shell escaping errors.

Enables AI agents to securely execute remote commands via SSH or JumpServer, with flexible gateway configuration and plugin-based matchers for JumpServer login interfaces.

Enables managing OpenI platform resources (login, query nodes, submit jobs, view logs) via natural language in Claude or Codex, following a kubectl/docker-style CLI.

This MCP server exposes a Telegram client that runs on the user's own account, enabling AI agents to read, search, send, and manage messages, press bot buttons, and work with chats, groups, and channels from the terminal. It is read-only by default, with writes requiring explicit human approval and every action logged for safety.

Zero-dependency MCP server to orchestrate a swarm of Claude Code / Codex sessions across WezTerm panes: any session can discover, spawn, prompt, and read the others via MCP tools. One session becomes the coordinator; crash isolation keeps peers alive; auto-handoff resumes sessions when context fills. Optional Telegram phone control.

Enables managing BOSH deployments via natural language by providing tools to login to a BOSH director and execute arbitrary BOSH commands.