MCP/HTTP Telegram Gateway — Multi-tenant, MTProto User API, 8 tools, multi-user Bearer auth, global search, session A...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Strong idea surface, weaker maintenance signal. Steal the pattern before you commit.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Archived repo plus maintenance drag means copy patterns, not the whole tool.
AI Agent
Cursor AI
Model
Claude
Fastest way to find out if fast-mcp-telegram belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add fast-mcp-telegram -- npx fast-mcp-telegramRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove fast-mcp-telegramNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ fast-mcp-telegram ← registers here
MCP/HTTP Telegram Gateway — Multi-tenant, MTProto User API, 8 tools, multi-user Bearer auth, global search, session ACL, Docker
Source: GitHub repository
Source check: No source check recorded
Upstream commit: June 11, 2026
Repository state: Archived by its owner
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.