npx skills add ...
npx skills add publora/skills --skill telegram-post
Use when the user wants to post or schedule to a Telegram channel or group through Publora, using a bot. Covers Telegram markdown, silent delivery, link previews and forward protection. Bot API caps media captions at 1,024 characters and videos at 50 MB. Not for other platforms (each has its own skill).
npx skills add publora/skills --skill telegram-post
Create and schedule posts to Telegram channels and groups using the Publora MCP server. Supports rich markdown formatting, photos, videos, and message delivery options.
Plans: Works on the free Starter plan. Current limits and pricing: publora.com/pricing.
/newbot and follow instructionscan_post_messages permission@username or t.me/username-100… chat ID, or the t.me/c/… link of any message in it (Copy Link on the message)t.me/+…) are rejected: the Bot API cannot identify a channel from themhttps://mcp.publora.com, authenticating with Authorization: Bearer sk_YOUR_API_KEY. In Claude Code:Claude Desktop, Cursor, Codex, OpenClaw and the claude.ai connector each need a different config file or flow: see client setup for the exact path and snippet.
If the MCP server is unavailable or returns errors, use the REST API directly:
Base URL: https://api.publora.com/api/v1
Authentication: Use x-publora-key header (NOT Authorization: Bearer):
Platform ID Format: telegram-{chat_id} where {chat_id} is the channel/group numeric ID from /platform-connections. A bot connection's chat ID is negative (-100…), so the ID has a double dash. Copy it verbatim; never rebuild it.
Example IDs: telegram--1001234567890, telegram--1002345678901
📖 Full API documentation: docs.publora.com
| Feature | Limit |
|---|---|
| Text message | 4,096 characters |
| Media caption | 1,024 characters (critical limit!) |
| Images | 10 MB max, 10 per media group |
| Image formats | JPEG, PNG, GIF, BMP, WebP |
| Video size | 50 MB max (not 4 GB - that's for users!) |
| Video formats | MP4, MOV, AVI, MKV, WebM |
| Rate limit | 30 msg/sec global, 20 msg/min per group |
Critical: Bot API has much lower limits than regular Telegram users. Videos over 50 MB and captions over 1,024 characters will fail.
Telegram uses its own markdown flavor with single asterisks for bold:
| Syntax | Result |
|---|---|
*bold* | bold |
_italic_ | italic |
`code` | inline code |
code | Code block |
[text](url) | hyperlink |
> text | Blockquote |
Note: This differs from standard Markdown where **double asterisks** make bold.
Create a new Telegram post.
Parameters:
platforms: Array with your Telegram connection ID (e.g., ["telegram--1001234567890"])content: Message text (supports markdown)scheduledTime: ISO 8601 UTC datetime. Optional: omit it and the post is created as a draft. Send a future time to schedule. A time five or more minutes in the past is rejected with SCHEDULED_TIME_IN_PAST, so for immediate posting use the current time plus a minute.mediaUrls: up to 10 public https image or video URLs. Publora downloads them server-side and attaches them before validation, so media and scheduling happen in one call. This is the one-shot alternative to the draft then get_upload_url then complete_media flow. Ingestion is rate-limited to 60 URLs per hour.Get presigned URL for media uploads.
Finalize a file uploaded through get_upload_url, after the presigned PUT succeeds. Optional, because scheduling also finalizes pending media, but calling it early surfaces format and probe errors before publish. Not needed for media attached with mediaUrls.
Parameters:
mediaId: the id returned by get_upload_urlList your connected accounts with their platform IDs. Call this first and copy the IDs verbatim; they are never guessable. A private channel has no public username: its username is null, so match it by displayName (the channel title).
Manage scheduled and draft posts. update_post also patches content and platforms on a draft or scheduled post, so fixing a typo or retargeting no longer means delete and recreate. delete_media and prune_media_reference clean up uploaded files.
Telegram-specific options available via REST API platformSettings.telegram:
| Option | Description |
|---|---|
disableNotification | Send silently (no sound) |
disableWebPagePreview | No link preview cards |
protectContent | Prevent forwarding/saving |
Caption-above-media is not settable: showCaptionAboveMedia is not an accepted key and sending it returns 400 PLATFORM_SETTING_UNKNOWN.
Note: platformSettings is accepted by the MCP create_post and update_post tools as well as over REST. The schema is strict: a mistyped platform or key is rejected with a validation error rather than silently dropped.
Important: Caption must be under 1,024 characters when posting with media.
Caption limit is 1,024 chars: When posting with media (images/videos), text is sent as a caption limited to 1,024 characters. Text-only messages allow 4,096 characters.
Video max 50 MB: Bot API limits videos to 50 MB (not 4 GB like regular users). Large videos will fail.
Bot must be admin: Your bot needs administrator role with can_post_messages permission. This is verified at connection time and re-checked by POST /test-connection/{platformId}, not before each post.
No mixed media: A single post cannot contain both images and videos.
Caption overflow: If caption exceeds 1,024 chars on a media post, it's sent as a separate reply message instead of being truncated.
| Error | Cause | Solution |
|---|---|---|
| "Bot not admin" | Bot missing admin permissions | Add bot as admin with can_post_messages |
| "Channel not found" | Wrong channel name/ID, or the bot is not in the channel | Verify @channelname or the -100… chat ID, and add the bot as an administrator |
| "Invite links cannot identify a channel for a bot" | A t.me/+… invite link was entered | Use the channel's -100… chat ID or a t.me/c/… message link |
MEDIA_CAPTION_TOO_LONG | Caption > 1,024 chars | Shorten caption or use text-only post |
| "Bad Request: file is too big" | File > 50 MB | Compress video/image to under 50 MB |
| "Mixed media not supported" | Images + video in same post | Use one media type per post |
# Get your connected platforms
curl -X GET "https://api.publora.com/api/v1/platform-connections" \
-H "x-publora-key: sk_your_api_key"
# Create a post
curl -X POST "https://api.publora.com/api/v1/create-post" \
-H "x-publora-key: sk_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"platforms": ["telegram--1001234567890"],
"content": "*Announcement*\n\nYour message here",
"scheduledTime": "2026-03-25T10:00:00Z"
}'Post this to my Telegram channel:
"*Product Update v2.5*
We have shipped the following improvements:
- _Faster API response times_ (avg 45ms)
- New `batch` endpoint for bulk operations
[Read the changelog](https://example.com/changelog)"Create a Telegram post with this formatting:
"*Important Update*
We're launching our new feature tomorrow at 10 AM UTC.
_What's new:_
- Feature A improvements
- Feature B release
[Read the full announcement](https://example.com/update)"Post this image to my Telegram channel with caption:
"*New Dashboard Preview*
Here's a sneak peek at our redesigned analytics dashboard."Schedule this for tomorrow at 8 AM Moscow time:
"*Good morning!* Here's your daily market summary..."