Post to Telegram from Cursor

Hermoso is a marketing MCP server: 850+ tools over one OAuth’d endpoint that let an agent research the ads already running in a market, generate finished image and video ads, publish them, and build the paid campaigns behind them. Cursor reaches all of it through one connection. This page is about one slice of that — what Cursor can actually do on Telegram, and what Telegram will not let it do.

Connect Hermoso to Cursor

1. Install and sign in.

   npm install -g hermoso && hermoso auth login

   Your browser opens once. Nothing to create and nothing to paste: the credential is stored owner-only in ~/.hermoso/config.json. On a machine with no browser, hermoso auth login --token hmk_… takes a key from MCP & CLI → Terminal & API keys instead.
2. Add it to ~/.cursor/mcp.json (or the project’s .cursor/mcp.json). No key goes in the file, because hermoso mcp reads the sign-in above:

   { "mcpServers": { "hermoso": { "command": "npx", "args": ["-y", "hermoso", "mcp"] } } }

3. Or use the one-click install from the MCP page. That deeplink installs the hosted URL and leaves authentication to Cursor’s own OAuth flow. Both work, they are just different prerequisites.
4. Ask Cursor for something. “Pull my three closest competitors’ longest-running ads and remix the best hook into a 9:16 video,” or “post this render to the channel.” The agent picks the tools; you approve the spend.

The block above runs the published hermoso npm package on your machine, which is why nothing is pasted and why the tool list costs nothing until a tool is called. If you use the deeplink instead, Cursor performs dynamic client registration against our authorization server and you never hold a key either.

Then connect Telegram itself, once, under Settings → Connectors in Hermoso by pasting a bot token from @BotFather, and add that bot to your channel as an administrator. There is no consent screen: the token is the credential, and the bot is who posts.

The Telegram tools Cursor gets

• post_to_telegram — sends a message as your bot to the chat you name: text up to 4,096 characters, or one photo, one video, or an album of 2 to 10 with photos and video mixed.
• schedule_post — queues it with its chatId on the same calendar as every other channel.
• list_telegram_chats — the chats that messaged the bot in the last 24 hours. It helps find an id, and it is not a list of every chat the bot is in.
• edit_telegram_message / pin_telegram_message — fix a message’s text or caption without losing its views, and pin or unpin the call to action.
• create_telegram_invite_link — a named invite link per campaign, with an optional expiry, member cap or join approval, so you can see who joined from where.
• telegram_account — the chat’s subscriber or member count, title, description and invite link.
• list_telegram_dms — what people sent the bot in the last 24 hours, newest first, to answer with post_to_telegram.
• delete_telegram_message — removes a message the bot sent, within Telegram’s 48-hour window, after a confirm step.

Telegram connects with a bot token, not a sign-in screen. Make a bot with @BotFather in Telegram, paste its token under Settings → Connectors, then add the bot to your channel as an administrator with Post Messages, or to a group as a member who can post. Hermoso posts as that bot, never as you. Two limits are Telegram’s and worth planning around: a bot gets no per-post views and no post history, so the subscriber count and named invite links are the numbers you have; and messages sent to the bot are kept for 24 hours, then gone. Publishing costs no credits.

Telegram limits worth knowing before you automate anything

Try it in Cursor

Ask for it in ordinary language — these are sentences, not a DSL:

“Post the release notes from CHANGELOG.md to our Telegram channel as a text message with link previews off, then pin it silently.”

That walks render_ad → post_to_telegram → pin_telegram_message → create_telegram_invite_link. Cursor surfaces each tool call in the composer before it runs, so a publish is a click rather than a side effect.

Cursor on Telegram: the part that bites

Pinning is silent by default, so pinning an announcement does not ping every member; ask for a notification if you want one. The bot needs pin rights as an administrator. On a text-only post the link preview is Telegram’s own default and can be switched off, which is worth doing when a changelog links to five things and the first one’s preview would take over the message.

Put the config in the project’s .cursor/mcp.json rather than the home directory when a repo should always run against one brand; hermoso auth login is what pins the workspace otherwise.

Research Telegram before you post

There is no Telegram ad library and no channel search in Hermoso, so it claims no competitor research on Telegram. Research the creative where it is public (the Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Reddit and Threads) and post the finished ad here.

The paid half

There are no Telegram ads in Hermoso, and we do not imply any. Telegram here is a channel you own and run through your bot: post, pin, edit, count subscribers and track invites. The paid tools cover Meta, Google Ads, Microsoft Advertising, Reddit Ads, LinkedIn, Pinterest, X Ads, TikTok Ads, Snapchat Ads, ChatGPT Ads and Apple Search Ads.

What Cursor cannot do on its own

An agent with a budget is only useful if the blast radius is bounded, so the fence is in the server rather than in a prompt. Every ad campaign, ad set, ad group and ad is created paused, and the status switches that arm real money refuse to run without an explicit confirmation flag. Every render is quoted first — hermoso_capabilities publishes each model’s exact credit cost before anything spends — and credits are reserved before the first provider call and settled at the exact cost afterwards, so a failed dispatch refunds rather than leaving you billed for nothing. Deletes are confirm-gated too, and every campaign tree is read back from the ad platform before your agent tells you what it built.

One step is deliberately yours: creating the bot with @BotFather and adding it to your channel. Everything after that is a tool call.

The rest of the matrix

From Cursor, post to: Facebook · Instagram · Threads · TikTok · YouTube · X · LinkedIn · Pinterest · Bluesky — or see everything Cursor can publish to.

Post to Telegram from: Claude · ChatGPT · Claude Code · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Perplexity · Le Chat

Frequently asked questions

Can Cursor post to Telegram?

Yes, through Hermoso's MCP server. Run npm install -g hermoso && hermoso auth login, then point ~/.cursor/mcp.json at npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in the file. Cursor then has 850+ tools, including the ones that publish to Telegram — and the ones that research the ads already running in your market and render the creative in the first place.

How do I connect Telegram to Cursor?

Two steps, once each. Run npm install -g hermoso && hermoso auth login, then point ~/.cursor/mcp.json at npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in the file. Then make a bot with @BotFather in Telegram, paste its token under Settings → Connectors in Hermoso, and add the bot to your channel as an administrator with Post Messages. After that Cursor publishes to Telegram as an ordinary tool call, naming the chat each time.

What is the Telegram caption limit when posting from Cursor?

A text-only Telegram message runs to 4,096 characters; once a photo or video is attached the text is a caption and the limit is 1,024. Hermoso says which budget applied. Hermoso enforces it when the post is created or queued, so Cursor is told immediately rather than failing later when nobody is watching.

Can Cursor run Telegram ads as well as posting?

No. There are no Telegram ads in Hermoso. Telegram here is a channel you run through your own bot: posts, pins, edits, invite links and the subscriber count.