mcp · handle codex_telegram_mcp
Telegram Account MCP · job 87%Telegram Personal MCP · job 76%tg-ai · job 74%telegram_mcp · job 74%Telegram MCP HTTP · job 75%CapyAgent Telegram MCP · job 79%Telegram Live MCP · job 75%Docker Telethon Plus · job 76%MCP Telegram Bridge · job 74%termgram · job 73%BotlineMCP · job 73%Telegram Agent by Nova · job 79%Teleloom · job 78%Telegram Business MCP · job 76%Telegram Assistant MCP · job 74%mcp_telegram · job 74%Telegram MCP · job 73%Telethon Plus · job 74%tgcli · job 81%secure_telegram_mcp · job 73%tg2codexMCP · job 82%Telegram Plugin · job 74%telepath · job 78%tgread · job 71%Cursor MCP Hooks Telegram · job 71%Telegram MCP Server · job 80%Telegram MCP · job 78%Telegram MCP Gateway · job 78%Telegram Context MCP · job 71%Telegram MCP · job 80%mcp-voice · job 71%Jarvis Telegram MCP · job 77%GhostPaw Telegram · job 74%tg-max-mcp · job 79%telegram-mcp-worker · job 72%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series