AwrAIter — Telegram channels

ai.awraiterPublished by awraiter.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Telegram channels you administer: analytics, content plans, scheduled publishing. No userbot

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & CollaborationData & Analytics

Overview

AI-generated overview

Lets an assistant read analytics for Telegram channels you administer and draft, schedule, and publish posts through your AwrAIter account.

What you can do
A remote MCP server for Telegram channels you administer. It exposes 25 tools covering channel and team listing, subscriber and reach analytics over 1-90 days, recent posts, semantic search over the channel's own posts and bound sources, draft generation from scraped sources, uniqueness and quality scoring, previews, content plans with free-slot lookup, brand brief and banlist management, and publishing or scheduling posts. Write tools are marked in the documentation; the rest are read-only.
When to use it
Useful if you run Telegram channels and want an assistant to pull performance data, plan a content calendar, and prepare or schedule posts without leaving the chat client. It fits editorial workflows where drafts are reviewed before publishing.
Requirements
A remote streamable HTTP endpoint at An AwrAIter account (sign in with Telegram) and at least one connected channel. Authentication is OAuth 2.1 with PKCE and dynamic client registration, or a personal access token sent as an Authorization Bearer header. Clients without OAuth need a token created in the panel under MCP connection.
Before you install
Write tools create, schedule, cancel, and publish posts, switch the active team, and change the channel's brand brief and banlist. The deep_analyze tool spends the team's AI credits. A token is bound to one user, one team, and one scope: read refuses all write tools, full allows everything the account can do in the panel. Tokens are shown once and can be revoked in the panel. Paid plans start at 9 EUR per month; payments are handled by Stripe.

Installation

In SourceWeft

  1. Open AwrAIter — Telegram channels in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.awraiter%2Ftelegram/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "awraiter-telegram-channels": {
      "type": "http",
      "url": "https://awraiter.ai/mcp"
    }
  }
}

README

AwrAIter MCP Server

[MCP Registry] [Transport] [Auth] [Docs]

A remote MCP server for the Telegram channels you administer: read analytics, draft posts from your own scraped sources, build content plans, schedule and publish — from inside ChatGPT, Claude, or any MCP-capable client.

Not a userbot. No phone number, no login code, no .session file. The server acts through your AwrAIter account and reaches only the channels of the team you authorize.

Русская версия · Connection guide · Tool reference · Team and invites · awraiter.ai

AI agent connecting this for someone? Follow AGENTS.md: exact commands for Claude Code, Codex, Gemini CLI and Cursor.

Server

URLhttps://awraiter.ai/mcp
TransportStreamable HTTP
AuthenticationOAuth 2.1 (PKCE, dynamic client registration) or a personal access token
Registry nameai.awraiter/telegram
AvailabilityEvery plan, including the free tier

Quick start

You need an AwrAIter account (sign in with Telegram) and at least one connected channel.

Claude (web / desktop)

Settings → Connectors → Add custom connector, paste the URL, press Connect, and confirm access for the team you want.

https://awraiter.ai/mcp

Claude Code

bash
claude mcp add --transport http awraiter https://awraiter.ai/mcp

Agent skill (Claude Code, Codex and other agents)

The AwrAiter_skills repository ships a skill with the full tool contract, authentication, the draft → check → preview → schedule workflow and the guardrails an agent should follow:

bash
# Claude Code — as a pluginclaude plugin marketplace add MediaZione/AwrAiter_skillsclaude plugin install awraiter@awraiter
# Codex and any other agent with skillsnpx skills add MediaZione/AwrAiter_skills --skill awraiter

ChatGPT

AwrAiter is not in the ChatGPT plugin catalog yet — add it as your own MCP server: Settings → Security and login → Developer mode, then chatgpt.com/plugins → +, paste the URL, keep OAuth and press Connect. In a chat, pick it from the tools menu. The ChatGPT/Codex desktop form has no OAuth option; connect it with a token instead (see below).

Clients that take a JSON config

json
{  "mcpServers": {    "awraiter": {      "type": "http",      "url": "https://awraiter.ai/mcp"    }  }}

Clients without OAuth (token auth)

Create a token in the panel under MCP connection — it is shown once, together with ready-to-paste snippets (Claude Code command, JSON config, cURL, Node.js) that already contain it — and send it as a header:

Authorization: Bearer YOUR_TOKEN

Step-by-step instructions for Claude, Claude Code, ChatGPT, Codex, Gemini CLI and Qwen Code are in docs/connect.md; ready-to-paste config files are in examples/.

Tools

29 tools. The ones that change something are marked ✍️ — everything else is read-only.

ToolWhat it does
list_teamsTeams you belong to; marks the active one
switch_team ✍️Switch the active team (membership is verified server-side)
list_channelsChannels owned by the active team
get_channelOne channel's profile: name, chat id, language, description
get_channel_statsSubscribers, reach, ER and dynamics over 1–90 days
get_channel_insightsWhat works for this audience, scored against the channel's own 30-day median
review_postsHow recent posts did against the channel's own posts at the same age: above, on par or below
get_recent_postsMost recent published posts, newest first
search_channel_contentSemantic search over the channel's own posts and source material
search_sourcesSearch the channel's bound sources
draft_from_sourcesFreshest scraped sources not yet used in a post
deep_analyze ✍️Deep AI analysis of channel performance — the one tool that spends the team's AI credits
check_uniquenessIs this draft a near-duplicate of existing posts or a copy of a source?
score_postData-grounded quality signal for a draft, specific to this channel
preview_postExact message that would be sent — title, body, media, formatting
create_post_from_text ✍️Save a ready-to-publish draft from text the assistant wrote, with photos, videos or music tracks by link
schedule_post ✍️Publish a draft now, or schedule it for a given time
cancel_scheduled_post ✍️Cancel a scheduled post by its plan id
get_content_planThe channel's plan configuration and its slots
create_content_plan ✍️Create a content plan for a channel
find_free_slotEarliest slot in the plan with no post yet
get_channel_memoryThe channel's brand brief, banlist and learnings journal
set_brand_brief ✍️Replace the channel's brand/tone guidance
add_banlist_entry ✍️Add a forbidden word to the channel's banlist
remove_banlist_entry ✍️Remove a word from the banlist
add_channel_learning ✍️Record a hypothesis or a proven learning about what works in the channel
remove_channel_learning ✍️Remove a journal entry
set_assist_mode ✍️How much the assistant coaches you: quiet, normal or coach
get_playbookStep-by-step operator playbook for a workflow

What each tool returns, and the exact scope it needs, is in docs/tools.md.

Authentication

OAuth 2.1 with PKCE and dynamic client registration; redirect URIs are restricted to HTTPS or HTTP loopback, authorization codes are single-use, and refresh tokens rotate. A token is bound to one user, one team and one scope.

Personal access tokens come in two scopes:

ScopeAllows
readRead-only tools; every ✍️ tool is refused server-side
fullEverything the account can do in the panel

Tokens are listed, and can be revoked, in the panel under MCP connection.

Security model

Userbot-style Telegram MCP serversAwrAIter
What you hand overPhone number, login code, session fileAn OAuth grant to your own account
What it can reachEverything your account can — DMs, groups, private materialOnly the channels of the team you authorized
How it publishesAs youThrough the panel's own service admin, with the same permission checks as the UI
If the token leaksYour whole Telegram accountRevoke the token in the panel; nothing else is exposed

Every write goes through the same channel-level access control as the panel, and rate limits apply per token. The full model, and how to report a vulnerability, are in SECURITY.md.

About AwrAIter

AwrAIter is a panel for people who run Telegram channels: weekly content plans, AI drafts in your channel's tone, scheduled publishing, and analytics for everything published — growth, reach, ER/ERR, per-post performance, channel comparison, export to XLSX or Google Sheets. One channel is free forever; paid plans start at €9/month. See awraiter.ai.

Support and legal

  • Questions and issues: awraiter.ai/support
  • Terms of Service · Privacy Policy
  • Operated by Mediazione Italia S.r.l. Payments are handled by Stripe; we never see card numbers.
  • Your channel content stays yours — we do not train models on it unless you explicitly opt in (off by default).

License

Documentation and examples in this repository are released under the MIT License. The AwrAIter service itself is proprietary.

Source: README.md at commit f091717

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts