Connect an AI agent to Telegram through MCP

An agent can prepare drafts, show previews and fill your saved templates in RichPost. You can continue in the editor, while a personal token determines which actions the agent can perform.

What the connection makes possible

MCP lets a compatible client call RichPost tools from a conversation with an agent. You can ask it to prepare an announcement, update a draft or create a post from a saved template. The result stays in your account so you can open it in the regular editor and review the text yourself.

You do not need to run your own server or download an application to connect to the hosted service. The client needs remote HTTP MCP support and a personal bearer token. A client that supports only OAuth cannot use this connection method. Support for installing a skill also depends on the client.

What to tell the agent

Give a compatible client the task below. It includes setup instructions and a separate verification step.

Connect RichPost for me. Read the agent setup instructions at https://richpost.ru/agents.md, configure MCP and install the skill if my client supports it. Ask me to issue a personal token. After connecting, check the available tools and studio status. Do not create or send a post to test the connection.

You can also share the link to this page. The instructions are public, while working tools require a token. A public link by itself does not give an agent access to your drafts.

Create a personal token

1. Sign in to RichPost with Telegram and open your account menu.
2. Open API and MCP tokens, then create a token. Give it a recognizable client name and an expiry date.
3. Choose the minimum permissions needed for the task. Draft permissions are usually enough for preparing text.
4. Save the token, shown only once, in the client's protected secret settings. Do not place it in a URL, public chat, screenshot or repository.

Choose the right permissions

• Read: inspect available data without changing drafts.
• Draft: work with text, drafts and templates without publishing permission.
• Publish: perform sending actions when the agreed task requires them.

Verify without publishing

After saving the configuration, the client may need a restart or approval of the new MCP server. The agent should retrieve the tool list and call studio_status successfully. A configuration entry or HTTP 200 response alone does not prove the tool completed without an error.

If the connection fails, check the token's expiry and role, the server address and how the client receives its secret. Do not send the token to another origin after an unexpected redirect. A separate token for each client makes it possible to revoke one connection without disabling the rest.

Your first working task

Start with a draft: “Prepare a meeting announcement, show a preview and save it for my review.” Supply the facts, links and intended formatting. Agree on the final text, destination channel and time before publishing. Connect the channel in the editor separately; issuing a token does not connect it automatically.

For text, see the Markdown guide. For structured data, try tables. To publish at a chosen time, use scheduled posts.

Setup documents

• Connection, client configuration and verification
• The installable RichPost skill
• A short index and the complete instructions in one file
• Capability discovery and the JSON description

Frequently asked questions

Open editor ↗