Postlyra MCP Server

Postlyra MCP

Postlyra.app connects AI chats to Telegram publishing. Create structured drafts, review previews and publish to a named connected channel now or on a schedule. For ChatGPT, install Postlyra from the published plugin directory; for compatible clients, use remote MCP.

Русский · Website · Connection guide

Save Telegram drafts, schedule publications and manage your content from an AI client. Postlyra is a hosted service. This repository contains public integration instructions, client configurations and diagnostics; it does not contain the private SaaS backend. No bot token or locally installed server is required.

Recorded compatibility evidence for hosted MCP 0.3.5. The endpoint exposes 32 tools. Desktop ChatGPT completed draft/card edits, browser source continuity, scheduling/moving/canceling, timed channel delivery and selected-message edit/delete with developer CSP enforcement enabled. The 804-test suite, typecheck/build and documentation checks passed. Group acceptance is blocked by a client safety review; remaining clients/devices are listed in client evidence. See the card guide. Registry version remains 0.2.0-rc.1.

Connect

• Remote MCP URL: https://postlyra.app/mcp
• Transport: Streamable HTTP
• Authentication: OAuth with PKCE, using your Postlyra account.

1. Open Postlyra and sign in with Telegram.
2. Add your channel or group under Connections and grant @PostlyraBot the necessary rights. You may save drafts before connecting a destination.
3. In ChatGPT, install Postlyra from the plugin directory. In other compatible AI clients, add the MCP URL. Follow the OAuth sign-in flow and review the requested permissions.
4. Ask the client to list your connected channels, then save a test draft. Configuration is complete only after authorization and a successful tool call.

Claude Code

claude mcp add --transport http --scope user postlyra https://postlyra.app/mcp

Open /mcp and authenticate Postlyra. Alternatively merge claude-code.json into the project's .mcp.json without replacing other servers. This is a Claude Code configuration, not a Claude Desktop remote-connector configuration. Official Claude Code instructions.

Codex

Merge codex.toml into your Codex config.toml, preserving the existing configuration. Then run codex mcp login postlyra to start the separate MCP OAuth flow. Official Codex instructions.

Cursor

Merge cursor.json into project .cursor/mcp.json or your global Cursor MCP configuration. Open the server settings and complete OAuth. Official Cursor instructions.

ChatGPT

In ChatGPT, open Postlyra in the plugin directory and install it. Connect your Postlyra account through OAuth, sign in with Telegram and review the requested permissions. Ask for your connected channels, save a draft and review its preview. Then explicitly name the channel and authorize publishing; for scheduling, include a date, time and time zone. Availability depends on your account and workspace policy. The published plugin is the primary installation path; it does not require Developer mode.

Claude

Open Customize → Connectors → Add custom connector, enter the public MCP URL and select Connect to authorize Postlyra. Team/Enterprise owners may need to add the connector for their organization first. Claude's remote connection originates from Anthropic's infrastructure, including when using Claude Desktop; use the account connector interface rather than the local desktop-extension configuration. Official Claude instructions.

Example requests

• “Save this text as a Postlyra draft titled Weekly recap.”
• “Find my draft about the autumn launch and show it.”
• “Find my music post and show its Postlyra card.”
• “Schedule this post in my connected channel for October 22, 2026 at 10:00 Europe/Moscow.”
• “Move that publication to October 23 at the same local time.”
• “Apply the current version only to the publication in my news channel.”
• “Cancel this scheduled publication.”
• “Show posts that need attention.”

Read permissions, media transfer, troubleshooting and the compatibility record.

Free Beta

5 channels/groups, 30 publications per day, 300 per 30-day period and 1 GB of media. For server-managed connected publications, one known target counts as one publication; technical retries are not additional publications. Native/inline flows use temporary holds and the confirmations available from Telegram, so exact recipient counting is not guaranteed. See confirmation limits. Publications include mandatory Postlyra attribution. AI-client subscriptions are separate.

Drafts and publications are distinct. Saving content does not automatically edit sent messages. Native/inline Telegram shares may lack identifiers required for later message management; the original Postlyra draft remains editable.

Diagnostics

Node.js 18+:

node scripts/diagnose.mjs

This makes read-only checks of public metadata and unauthenticated MCP discovery. It does not authenticate, access drafts or publish anything.

Distribution status

server.json is published as io.github.prof-1t/postlyra-mcp, version 0.2.0-rc.1. The official Registry API confirmed an active entry on September 11, 2026. The production endpoint also exposes the expanded tool metadata. Postlyra is also published in the ChatGPT plugin directory. The MCP Registry and ChatGPT directory are separate distribution channels; a listing does not establish independent live validation of every AI client. See the release record.

Useful guides

• Telegram MCP server: English · Русский.
• Publish to Telegram from Claude: English · Русский.
• Create editable tables in Telegram: English · Русский.

Support

Postlyra support · Privacy · Terms

Never include access tokens, authorization codes, private previews or channel content in public issues.

Official client references

Claude Code MCP · MCP remote registry · Codex MCP · Cursor MCP