What is the key difference between Telegram MCP and Callcenter.js MCP?

Telegram MCP belongs to the Communication category with local stdio execution, while Callcenter.js MCP belongs to the Communication category with local stdio execution.

How do I install Telegram MCP or Callcenter.js MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Telegram MCP and Callcenter.js MCP free or paid?

Telegram MCP operates under a Free / Open Source model (API Key required). Callcenter.js MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Telegram MCP lists 6 tools with 3 views and 348 GitHub stars. Callcenter.js MCP lists 6 tools with 4 views and 25 GitHub stars.

Can I use both Telegram MCP and Callcenter.js MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Telegram MCP vs Callcenter.js MCP

In-depth architectural comparison of the Telegram MCP and Callcenter.js MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Telegram MCP

Communication · Local stdio

Quality: 56/100 (Good) | Auth: API Key required

Callcenter.js MCP

Communication · Local stdio

Quality: 43/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Telegram MCP if you need specialized Communication tools running via a local process. Choose Callcenter.js MCP if your workspace requires Communication integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Telegram MCP when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TG_APP_ID, TG_API_HASH.
Primary tools included: Retrieve current account information, List dialogs with unread filtering, Fetch messages from a dialog.

Explore Telegram MCP Details

Choose Callcenter.js MCP when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SIP_USERNAME, SIP_PASSWORD, SIP_SERVER_IP, OPENAI_API_KEY.

Feature & Specification Comparison

Specification	Telegram MCP chaindead Communication	Callcenter.js MCP gerkensm Communication
Summary	Telegram API integration for accessing user data, managing dialogs (chats, channels, groups), retrieving messages, and handling read status	An MCP server to make phone calls using VoIP/SIP and OpenAI's Realtime API and observe the transcript.
Category & Scope	Communication

Tools & Capabilities Breakdown

Telegram MCP Tools (6)

Retrieve current account information

List dialogs with unread filtering

Fetch messages from a dialog

Mark dialogs as read

Send draft messages

Override the JSON Schema version

Callcenter.js MCP Tools (6)

MCP, CLI, and TypeScript interfaces

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Telegram MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "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"
      }
    }
  }
}

Callcenter.js MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "gerkensm-callcenter-js-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "github:gerkensm/callcenter.js-mcp"
      ],
      "env": {
        "SIP_USERNAME": "YOUR_SIP_USERNAME_HERE",
        "SIP_PASSWORD": "YOUR_SIP_PASSWORD_HERE",
        "SIP_SERVER_IP": "YOUR_SIP_SERVER_IP_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Telegram MCP is categorized under Communication and uses a local stdio subprocess. In contrast, Callcenter.js MCP belongs to Communication using local stdio subprocess. Select Telegram MCP when you need capabilities focused on communication and Callcenter.js MCP when you require tools for communication.

More alternatives to Telegram MCP More alternatives to Callcenter.js MCP Communication category hub