| FMRS | 38 / 100 · D | 70 / 100 · B |
|---|
| Reliability | 6 / 20 | 9 / 20 |
|---|
| Security and permissions | 6 / 20 | 16 / 20 |
|---|
| Maintenance | 2 / 20 | 14 / 20 |
|---|
| Documentation | 12 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 14 / 20 |
|---|
| Best for | - Developers wanting to integrate Spotify control into AI assistants or custom apps.
- Scenarios requiring quick implementation of playback, playlist management, volume adjustment, etc.
- Users who already have a Spotify Premium account and a developer application.
| - Developers who want to integrate Telegram into MCP clients like Claude
- Automation scenarios that need to manage multiple Telegram accounts
- Building custom Telegram bots or workflows
- Scenarios that require secure file operation path restrictions
|
|---|
| Not for | - Users without a Spotify Premium account, as some features (playback control, volume) require Premium.
- Those expecting an officially supported or production-grade solution, as this server is third-party and unverified.
- Remote access over HTTPS, as this server only supports stdio.
| - Use cases requiring official Bot API features (this server uses a user client)
- Non-technical users who want a fully managed solution
- Multiple processes using the same session without lock management
|
|---|
| Required permissions | - Access to user's Spotify data, including playlists, liked songs, recent playback.
- Control playback, including play, pause, skip, volume, etc.
- Modify user's playlists (create, delete, add, remove tracks).
- Access device information (available devices, current device, etc.).
| - Requires Telegram API ID and API Hash
- Requires the user's Telegram session string (equivalent to account access)
- Can send messages, media, contacts, and settings to any allowed chat
- Can create or modify groups, channels, and chat settings
- Can access and operate on the user's media files and contacts
|
|---|
| Risks and side effects | - Security: OAuth tokens stored locally in spotify-config.json; if leaked, could lead to account misuse.
- Privacy: AI assistants may access personal data like playback history and playlists.
- Misoperation: AI might perform unintended actions like changing playback or modifying playlists.
- Unofficial: Not maintained by Spotify, may have bugs or security vulnerabilities.
| - Session string leakage could lead to account compromise
- Sending messages may raise privacy or security concerns
- Prompt injection: Telegram content may be maliciously crafted, so precautions are needed
- Risk of using unofficial PyPI package name; avoid pip install telegram-mcp
- Concurrent clients using the same session may cause AuthKeyDuplicatedError
|
|---|
| Supported clients | Claude Desktop, Cursor, Cline | Claude Desktop, Cursor, Claude Code, Codex |
|---|
| Tools | 27 | 76 |
|---|