Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Telegram channels you administer: analytics, content plans, scheduled publishing. No userbot
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://awraiter.ai/mcpRun this in your terminal
claude mcp add --transport http telegram https://awraiter.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"telegram": {
"url": "https://awraiter.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"telegram": {
"type": "http",
"url": "https://awraiter.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://awraiter.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain awraiter.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
| URL | https://awraiter.ai/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 (PKCE, dynamic client registration) or a personal access token |
| Registry name | ai.awraiter/telegram |
| Availability | Every plan, including the free tier |
You need an AwrAIter account (sign in with Telegram) and at least one connected channel.
Settings → Connectors → Add custom connector, paste the URL, press Connect, and confirm access for the team you want.
https://awraiter.ai/mcp
claude mcp add --transport http awraiter https://awraiter.ai/mcp
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:
# Claude Code — as a plugin
claude plugin marketplace add MediaZione/AwrAiter_skills claude plugin install awraiter@awraiter
npx skills add MediaZione/AwrAiter_skills --skill awraiter
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).
{
"mcpServers": { "awraiter": { "type": "http", "url": "https://awraiter.ai/mcp" } } }
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](docs/connect.md); ready-to-paste config files are in [examples/](examples/).
29 tools. The ones that change something are marked ✍️ — everything else is read-only.
| Tool | What it does |
|---|---|
list_teams | Teams you belong to; marks the active one |
switch_team ✍️ | Switch the active team (membership is verified server-side) |
list_channels | Channels owned by the active team |
get_channel | One channel's profile: name, chat id, language, description |
get_channel_stats | Subscribers, reach, ER and dynamics over 1–90 days |
get_channel_insights | What works for this audience, scored against the channel's own 30-day median |
review_posts | How recent posts did against the channel's own posts at the same age: above, on par or below |
get_recent_posts | Most recent published posts, newest first |
search_channel_content | Semantic search over the channel's own posts and source material |
search_sources | Search the channel's bound sources |
draft_from_sources | Freshest 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_uniqueness | Is this draft a near-duplicate of existing posts or a copy of a source? |
score_post | Data-grounded quality signal for a draft, specific to this channel |
preview_post | Exact 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_plan | The channel's plan configuration and its slots |
create_content_plan ✍️ | Create a content plan for a channel |
find_free_slot | Earliest slot in the plan with no post yet |
get_channel_memory | The 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_playbook | Step-by-step operator playbook for a workflow |
What each tool returns, and the exact scope it needs, is in [docs/tools.md](docs/tools.md).
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:
| Scope | Allows |
|---|---|
read | Read-only tools; every ✍️ tool is refused server-side |
full | Everything the account can do in the panel |
Tokens are listed, and can be revoked, in the panel under MCP connection.
| Userbot-style Telegram MCP servers | AwrAIter | |
|---|---|---|
| What you hand over | Phone number, login code, session file | An OAuth grant to your own account |
| What it can reach | Everything your account can — DMs, groups, private material | Only the channels of the team you authorized |
| How it publishes | As you | Through the panel's own service admin, with the same permission checks as the UI |
| If the token leaks | Your whole Telegram account | Revoke 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](SECURITY.md).
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.
Documentation and examples in this repository are released under the MIT License. The AwrAIter service itself is proprietary.