Telegram MCP vs Lycatra
A side-by-side look at the Telegram MCP and Lycatra MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LycatraCommunication · Remote HTTP/SSEConnect agents to Lycatra knowledge, memory, collaboration, schedules, notifications, and teams.40FairAuth: not declaredVerdict: choose Telegram MCP for communication work as a local process; choose Lycatra for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Telegram MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TG_APP_ID, TG_API_HASH.
LChoose Lycatra when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Lycatra | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 56/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | TG_APP_IDTG_API_HASH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 348 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Telegram MCP | View Lycatra |
Tools & capabilities
Telegram MCP tools
No tool names declared yet. Check the project README from the listing page.
Lycatra tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Telegram MCP
{
"mcpServers": {
"chaindead-telegram-mcp": {
"command": "npx",
"args": [
"-y",
"@chaindead/telegram-mcp"
],
"env": {
"TG_APP_ID": "YOUR_TG_APP_ID_HERE",
"TG_API_HASH": "YOUR_TG_API_HASH_HERE"
}
}
}
}
Lycatra
{
"mcpServers": {
"lycatra": {
"url": "https://lycatra.com/api/mcp"
}
}
}
Frequently asked questions
Telegram MCP is categorized under Communication and uses a local stdio subprocess. Lycatra belongs to Communication and uses a remote HTTP/SSE transport. Pick Telegram MCP for communication work and Lycatra for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Telegram MCP is listed as free. Auth: api key required. Lycatra has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add chaindead-telegram-mcp and lycatra as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Telegram MCP has a quality signal of 56/100 (Good) with 3 views, 0 installs and 348 GitHub stars. Lycatra has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
