Explain that Telegram user auth for this plugin happens outside the MCP server because Codex spawns MCP servers headlessly over stdio.
Tell the user to generate api_id and api_hash at https://my.telegram.org/apps.
Instruct them to run the login command from the plugin checkout root (the directory that contains mcp_server/; in a repo checkout that is telegram/, in an installed bundle it is ~/.codex/plugins/cache/<marketplace>/telegram/<version>/): uv run --project ./mcp_server codex-telegram login — or pass the absolute path, e.g. uv run --project /path/to/telegram/mcp_server codex-telegram login, to run it from anywhere.
Mention the prompts they will see: API ID, API hash, phone number, login code, and optional 2FA password.
If the OS keyring is unavailable, instruct them to rerun and let the login flow prompt for a master key, or set CODEX_TELEGRAM_MASTER_KEY in the environment first.
Once login succeeds, use get_session_info or get_me to confirm the account.
For diagnostics without valid auth (storage backend, cache state, runtime paths), call the telegram_diagnostics tool — it never requires a connected session.
If they want to clear auth, run uv run --project ./mcp_server codex-telegram logout from the same directory (or use the logout MCP tool with confirm=true if destructive tools are enabled).

Más de este repositorio

mismo repositorio

telegram-media-inspect

bchewy/codex-telegram-plugin

Use when the user asks to inspect, watch, listen to, transcribe, or understand Telegram voice notes, video notes, audio files, videos, or other message media.

2026-06-1130

telegram-aggregate

bchewy/codex-telegram-plugin

Use when cached Telegram volume or sender stats are requested.

2026-06-1030

telegram-manage-groups

bchewy/codex-telegram-plugin

Use when Telegram groups, channels, members, or admins are requested.

2026-06-1030

telegram-search

bchewy/codex-telegram-plugin

Use when finding Telegram messages by query or window.

2026-06-1030

telegram-send

bchewy/codex-telegram-plugin

Use when drafting, sending, replying, forwarding, or scheduling Telegram.

2026-06-1030

telegram-summarize

bchewy/codex-telegram-plugin

Use when Telegram summaries, unread catch-ups, or recaps are requested.

2026-06-1030

name	telegram-login
description	Use when Telegram auth setup, reset, or diagnostics are requested.

Explain that Telegram user auth for this plugin happens outside the MCP server because Codex spawns MCP servers headlessly over stdio.
Tell the user to generate api_id and api_hash at https://my.telegram.org/apps.
Instruct them to run the login command from the plugin checkout root (the directory that contains mcp_server/; in a repo checkout that is telegram/, in an installed bundle it is ~/.codex/plugins/cache/<marketplace>/telegram/<version>/): uv run --project ./mcp_server codex-telegram login — or pass the absolute path, e.g. uv run --project /path/to/telegram/mcp_server codex-telegram login, to run it from anywhere.
Mention the prompts they will see: API ID, API hash, phone number, login code, and optional 2FA password.
If the OS keyring is unavailable, instruct them to rerun and let the login flow prompt for a master key, or set CODEX_TELEGRAM_MASTER_KEY in the environment first.
Once login succeeds, use get_session_info or get_me to confirm the account.
For diagnostics without valid auth (storage backend, cache state, runtime paths), call the telegram_diagnostics tool — it never requires a connected session.
If they want to clear auth, run uv run --project ./mcp_server codex-telegram logout from the same directory (or use the logout MCP tool with confirm=true if destructive tools are enabled).