Telegram MCP Server (chigwell) vs Zapier MCP Server (Remote)
A side-by-side comparison of two Communication servers — tools, transport, auth, maintenance, and copy-paste config for each.
| Telegram MCP Server (chigwell) Full Telegram user-account MCP via MTProto: read chats, manage groups, send messages Verified stdio (local) API key Python | Zapier MCP Server (Remote) Remote MCP bridging assistants to Slack, Gmail, Teams and thousands of comms apps Verified HTTP (remote) API key Stale Hosted | |
|---|---|---|
| Category | Communication | Communication |
| Language | Python | Hosted |
| Transport | stdio (local) | HTTP (remote) |
| Auth | API key | API key |
| GitHub stars | 1.2k | 295 |
| Last commit | 1 month ago | unknown |
| Verified | ||
| Actively maintained | ||
| Install | git clone https://github.com/chigwell/telegram-mcp && cd telegram-mcp && uv sync && uv run main.py | Generate your personal Zapier MCP server URL at https://mcp.zapier.com and add it as a remote HTTP MCP endpoint |
| Repo | Open | Open |
Verdict
Pick Telegram MCP Server (chigwell) if you prefer the more popular, battle-tested option, and you want a local (stdio) server that keeps data on your machine.
Pick Zapier MCP Server (Remote) if you want the official, vendor-maintained server, and you want a hosted/remote server with nothing to install.
Add Telegram MCP Server (chigwell)
git clone https://github.com/chigwell/telegram-mcp && cd telegram-mcp && uv sync && uv run main.pyPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"telegram-mcp-server-chigwell": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/telegram-mcp",
"run",
"main.py"
],
"env": {
"TELEGRAM_API_ID": "<your-telegram-api-id>",
"TELEGRAM_API_HASH": "<your-telegram-api-hash>",
"TELEGRAM_SESSION_STRING": "<your-generated-session-string>"
}
}
}
}Add Zapier MCP Server (Remote)
Generate your personal Zapier MCP server URL at https://mcp.zapier.com and add it as a remote HTTP MCP endpointPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"zapier-mcp-server-remote": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.zapier.com/api/mcp/a/<your-account>/mcp?serverId=<your-server-id>"
]
}
}
}Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.
FAQ
Telegram MCP Server (chigwell) or Zapier MCP Server (Remote) — which is better?
Pick Telegram MCP Server (chigwell) if you prefer the more popular, battle-tested option, and you want a local (stdio) server that keeps data on your machine. Pick Zapier MCP Server (Remote) if you want the official, vendor-maintained server, and you want a hosted/remote server with nothing to install.
Can I use both Telegram MCP Server (chigwell) and Zapier MCP Server (Remote)?
Yes — MCP clients let you enable multiple servers at once. Add both configs to your client's mcpServers and use whichever tool fits the task.
Do Telegram MCP Server (chigwell) and Zapier MCP Server (Remote) work with Claude, Cursor and Windsurf?
Both do. Copy the per-client config below into Claude Desktop, Cursor, or Windsurf.