Telegram MCP for Claude and Codex

Connect with browser OAuth

Add this exact remote MCP URL. Your client discovers Chiho's authorization server, opens the Chiho consent flow, and reconnects automatically after approval.

codex mcp add chiho --url https://api.chiho.ai/mcp
codex mcp login chiho

Start with a small Telegram workflow

MCP connects your AI client to tools. A skill supplies instructions for using those tools on a particular task. Connect your Telegram account in Chiho first, complete browser authorization, and choose the account or team context you intend to use.

For a first request, try: “Summarize the open questions in this selected conversation and cite the messages that support each point. Do not send a reply.” Review the result against the source conversation before expanding the task.

• Follow-up tasks: identify commitments and propose a next action.
• Lead qualification: organize known requirements and unanswered questions.
• Meeting recaps: prepare a summary for review with decisions and owners.

Browse the full skills catalog, read the AI agent connection guide, or explore the Chiho AI assistant.

Permissions and action safety

A browser OAuth connection grants the current Chiho Telegram and CRM capabilities after explicit consent. That includes read tools and available actions such as preparing or sending messages, managing folders, inviting members, updating CRM data, and managing automation rules.

MCP metadata helps clients distinguish reads, writes, destructive changes, and external effects, but prompt behavior depends on the client's tool settings. Chiho requires stored previews and approval for member invitations and group exits, and can require it for batch sends. Other writes can execute directly after any client-side control, so review tool permissions and action targets before granting access.

Headless automation

Existing personal access tokens are for controlled headless jobs and advanced setups only. Do not paste them into Claude, Codex, ChatGPT, plugin manifests, shared configuration, or support messages. Interactive users should always use browser OAuth.

Environments and discovery

Production uses only https://api.chiho.ai/mcp. Isolated pre-production testing uses https://stagingapi.chiho.ai/mcp. The protected-resource discovery document is available at:

• https://api.chiho.ai/.well-known/oauth-protected-resource/mcp

Connection questions

Why can’t the client see my conversations?

Check that Telegram is connected in Chiho and that you authorized the intended Chiho account and team. Confirm the remote URL above. If authorization expired or was revoked, reconnect through the client’s browser login flow. Share error messages with support after removing tokens and private conversation content.

Does installing a skill grant account access?

No. A skill is a workflow instruction file. Account access comes from the separate authorized connection. Read each skill’s scope and action guidance before running it.

Is this the same as tgchats local?

No. This page describes the hosted Chiho connection. The separate tgchats local project documents a local CLI and MCP setup. Choose the setup that matches your intended storage and operating environment.