Post to Telegram from an agent
PostWharf ships a Model Context Protocol server, so Claude and other MCP clients can draft, queue and check Telegram posts as tools rather than as scraped UI.
Connect it
claude mcp add --transport http \ wharf https://mcp.postwharf.com/mcp \ --header "Authorization: Bearer $POSTWHARF_KEY"
The key scopes every call to one workspace, so an agent can only ever act on the brand you hand it. Find it in the dashboard under API keys.
What the agent can do with Telegram
What Telegram accepts
4,096 characters, counting one message. Up to 10 images or 10 videos per post — and the two can travel together.
Read from the table the API enforces, so a post over 4,096 is refused when you create it rather than truncated on the way to Telegram.
Asking for it in practice
# to Claude, with the connector attached
"Draft three Telegram posts about the new release,
queue the best one for Tuesday morning,
and tell me once it is live."
The agent drafts and queues; the delivery receipt tells you what actually published. Posts to channels you administer via a bot token you control.
Every other network
Instagram · TikTok · X · LinkedIn · YouTube · Facebook · Threads · Pinterest · Bluesky · Reddit · Discord · Snapchat · WordPress