telegram-channel-mcp-server

Need copy. That's okay.

But note our first table translation row count. Maybe keep separator exactly as original. Let's include original separators in final. Need not be nested in code.

Table header "変数" in first column, but original separator uses pattern with leading hyphens; okay.

Let's reconstruct final with original separators to be faithful. But since I'm translating text, using those long separators is fine. But the "exact structure" is more important than readability. Let's keep.

Need "GXP1", "GXP3" all exact.

Need "GXP2" and "GXP4" exact.

Now another concern: "GXP1" appears after "## Installation". Maybe it's an blank token. In output should appear "GXP1" on its own line. yes.

Need "Layout:" in original begins with "Layout:" after GXP4 and a paragraph. We translate "構成:" maybe okay. "Layout" is code? Not exactly. Keep "ファイル構成:" maybe. But original says "Layout:" as term. To preserve structure, translate to "構成:".

Need "media resolution" maybe phrase "メディアの解決" actual Japanese "メディアの解決" (retain technical wording). "response formatting" = "レスポンスのフォーマット" or "レスポンス整形". Let's do "レスポンスの整形".

Need "shared zod schemas" "共有 zod スキー" maybe "zod schema" not arbitrary, "zod" is package name verbat. Write "共有 zod スキーマ". Good.

Let's ensure "zod" name? Actually "zod" is library. "shared zod schemas" preserve "zod". Fine.

Need "MarkdownV2" keep. "MarkdownV2" library? telegram parse_mode "MarkdownV2" exact. Good.

Need "http(s)" code span. It is code span `http(s)`? Original "a public `http(s)` URL" yes. In translation use "公開の `http(s)` URL". Good.

Need "file_id" code. Good.

Need "mcp://" not present.

Let's revisit "MCP server (stdio)" — "MCP サーバー（stdio）" in Japanese, parentheses "（stdio）". But instruction preserve product names. "stdio" is lowercase. Fine.

Should we keep "(stdio)" as ASCII in original? It said preserve URI schemes, etc. But "stdio" not code. We can keep as " (stdio)" or "（stdio）"? To preserve structure, maybe keep parentheses " (stdio)" (same). Japanese prose often use full-width parentheses but original uses ASCII. "Preserve document structure" not typography. But maybe "MCP server (stdio)" is a noun phrase; I'd keep " (stdio)" approximately. However, "MCP Server (stdio)" appears at beginning. Use "MCP サーバー (stdio)" with ASCII parentheses to align original. For "via the Bot API", use "Bot API を介して". Good.

Need tips: Telegram Chinese? Japanese. Good.

Table row "TELEGRAM_BOT_TOKEN": "translate 限定": "Bolt from @BotFather. The bot must be a Standardity admin..." Fine.

Could "permission「Post messages」" in original quotes need maintain? In translated text, permission label is in English "Post messages". We can render "「メッセージを投稿」". This is not verbatim, but text. If exact perhaps better "「Post messages」" while Japanese context? The instruction says translate prose; no need keep permission English. But "Post messages" is not code, but likely an API text? It's a permission name in Telegram UI, untranslated in code. Hmm. The server sends messages, not permission. I can keep "「Post messages」" if preserving. But Japanese translation may be more useful. Maybe keep English in quote: 「メッセージを投稿("Post messages")」? Too much. Let's use "「メッセージを投稿」". Fine.

Need thought: The bot must be "channel admin with the "Post messages" permission". In Japanese, Telegram's admin rights called "投稿" perhaps "投稿権限". Use "投稿権限" not "Post messages". Good.

Let's now create final. Ensure there is no markdown code fence. 

Need decide whether to use "## 設定" or "## 環境変数". "Config" = 設定.

Need "Claude Code" GXP2: since unknown, GXP2. Fine.

Let's produce a polished translation: