danog/madelineproto

Async PHP client API for the telegram MTProto protocol

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 34 minutes ago
Added to GitGenius on September 19th, 2026
Created on June 23rd, 2016
Open Issues & Pull Requests: 75 (+0)
GitHub issues: Enabled
Number of forks: 906
Total Stargazers: 3,518 (+0)
Total Subscribers: 198 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 63
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 444 days
Stale 30+ days: 59
Stale 90+ days: 53

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • waiting feedback (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

MadelineProto is an async PHP client library for the Telegram MTProto protocol that enables direct interaction with Telegram without relying on the bot API.

The library solves the problem of accessing Telegram's full functionality from PHP by implementing the MTProto protocol directly. It supports authentication via phone number for user accounts or bot tokens, both using the MTProto API rather than Telegram's HTTP bot API. The tool is fully asynchronous, built on AMPHP, allowing concurrent operations and non-blocking I/O patterns typical of modern async PHP applications.

Developers should choose this library when they need deeper Telegram integration than the official bot API provides, such as accessing secret chats, making VoIP calls, working with Stories, or building userbot functionality. It suits projects requiring direct protocol access rather than the limited feature set of the bot API. The library is approved by Telegram and includes examples ranging from simple bots to complex applications like VoIP webradios and story downloaders. For those evaluating alternatives, the README emphasizes that this approach uses MTProto directly rather than wrapping the bot API, giving access to capabilities unavailable through official HTTP endpoints.

Development activity shows consistent maintenance with active community engagement through official support channels. The project maintains comprehensive documentation and provides multiple standalone libraries extracted from its core components, indicating a mature codebase with well-separated concerns. Examples and real-world projects built with the library are actively curated and documented, suggesting ongoing investment in developer experience.