telegram-mcp
Related Servers
Alternatives to telegram-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to generate images and iteratively edit them using OpenAI's gpt-image-2 models, with session management, background job polling, and local file saving.8556 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables local image generation through a ChatGPT web account, downloading original files with paths, sizes, and checksums while keeping responses compact. Supports batched requests and resumable recovery without embedding images in model context.MIT
- FlicenseAqualityCmaintenanceAsynchronous image generation MCP server that submits prompts and automatically downloads images locally.5-

beeimg-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables uploading images to BeeIMG, deleting images, and retrieving premium account info through a local stdio MCP server.MIT- FlicenseNot gradedqualityDmaintenanceEnables image generation and editing via third-party relay services. Returns local file paths and Markdown display hints.-
- AlicenseNot gradedqualityCmaintenanceA zero-dependency stdio MCP server that lets a model set its own QQ avatar from an image the user just sent (by message ID, URL, local path, or base64) and update its nickname or signature, fetching, magic-number validating, and uploading the image entirely on the local host instead of pushing base64 into the model context. All calls are locked to the owner's private chat, with group-chat attempts rejected and no parameter able to override the owner.MIT
TDQS
Scored across 2 tools
The two tools are clearly distinct: get_latest_image retrieves a previously posted photo, while wait_for_next_image blocks for a new one. The use cases do not overlap in an ambiguous way.
Both names follow a verb-noun structure and clearly communicate function. The slight mix of 'get_' and 'wait_for_' is a minor deviation but still predictable.
Two tools is at the low end of a reasonable scope for a narrow image-receiving server. They cover the core need without bloat, but the server feels rather thin.
The pair covers the two key workflows: retrieving a previous screenshot and waiting for a new one. Missing features like explicit image search or sending could be useful, but they are not essential for the server's obvious intent.