Skip to main content
hc
Submit
mcpSource-backed
Telegram MCP Server logo

Telegram MCP Server

Telethon-powered MCP server for connecting Claude to Telegram accounts, chats, messages, contacts, media, folders, groups, channels, profile settings, and read-only or full account workflows.

by chigwell · submitted by oktofeesh1·added 2026-06-06·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/telegram-mcp-server
Source URLs
https://raw.githubusercontent.com/chigwell/telegram-mcp/main/README.md, https://github.com/chigwell/telegram-mcp
Brand
Telegram MCP Server
Brand domain
telegram.org
Brand asset source
brandfetch
Safety notes
Telegram MCP Server can read chats and messages, send, schedule, edit, delete, forward, and pin messages, mark chats read, create polls, press inline buttons, manage contacts, manage groups and channels, upload or download media, and update profile settings when write tools are exposed., A Telegram session string has the normal authority of the Telegram account inside the server process; read-only mode limits the MCP tool surface but does not reduce the underlying session authority., The upstream README warns that the PyPI `telegram-mcp` name is owned by a different project, so do not pass Telegram API credentials or session strings to that package., File-path tools are disabled until allowed roots are configured; keep upload and download roots narrow when enabling media or file operations., Require human approval before sending, editing, deleting, forwarding, pinning, reacting, inviting, banning, changing permissions, or updating profile and privacy settings., Use separate Telegram accounts for testing, monitor Telegram rate limits and platform rules, and keep proxies or multi-account routing explicit.
Privacy notes
Telegram API IDs, API hashes, session strings, account labels, chat titles, usernames, phone-adjacent identifiers, messages, media, contacts, group membership, profile photos, user status, read receipts, drafts, and folder metadata can be exposed to the MCP client., Chat history and media can contain private conversations, personal data, business records, access links, invite links, documents, photos, voice notes, stickers, GIFs, and user-controlled prompt-injection text., The project includes output sanitization for user-controlled content, but sanitized Telegram content should still be treated as untrusted model input., Store session strings like passwords, keep them out of shell history and shared logs, and revoke sessions if they are exposed., Review MCP transcripts, downloaded media folders, Telegram session files, and proxy logs before sharing or retaining them.
Author
chigwell
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

30 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

6 to clear

Platforms

2 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup. Have accounts and credentials ready first.

0/6 ready
Account & credentials3Install & runtime1General230 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 5 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes, network access.

5 areas
  • SafetyNetwork accessTelegram MCP Server can read chats and messages, send, schedule, edit, delete, forward, and pin messages, mark chats read, create polls, press inline buttons, manage contacts, manage groups and channels, upload or download media, and update profile settings when write tools are exposed.
  • SafetyCredentials & tokensA Telegram session string has the normal authority of the Telegram account inside the server process; read-only mode limits the MCP tool surface but does not reduce the underlying session authority.
  • SafetyCredentials & tokensThe upstream README warns that the PyPI `telegram-mcp` name is owned by a different project, so do not pass Telegram API credentials or session strings to that package.
  • SafetyNetwork accessFile-path tools are disabled until allowed roots are configured; keep upload and download roots narrow when enabling media or file operations.
  • SafetyPermissions & scopesRequire human approval before sending, editing, deleting, forwarding, pinning, reacting, inviting, banning, changing permissions, or updating profile and privacy settings.
  • SafetyGeneralUse separate Telegram accounts for testing, monitor Telegram rate limits and platform rules, and keep proxies or multi-account routing explicit.
  • PrivacyCredentials & tokensTelegram API IDs, API hashes, session strings, account labels, chat titles, usernames, phone-adjacent identifiers, messages, media, contacts, group membership, profile photos, user status, read receipts, drafts, and folder metadata can be exposed to the MCP client.
  • PrivacyData retentionChat history and media can contain private conversations, personal data, business records, access links, invite links, documents, photos, voice notes, stickers, GIFs, and user-controlled prompt-injection text.
  • PrivacyGeneralThe project includes output sanitization for user-controlled content, but sanitized Telegram content should still be treated as untrusted model input.
  • PrivacyCredentials & tokensStore session strings like passwords, keep them out of shell history and shared logs, and revoke sessions if they are exposed.
  • PrivacyCredentials & tokensReview MCP transcripts, downloaded media folders, Telegram session files, and proxy logs before sharing or retaining them.

Disclosure: Community-maintained Apache-2.0 MCP server for Telegram via Telethon. The repository explicitly warns that the PyPI `telegram-mcp` name is unrelated, so install from a trusted source checkout or explicit Git URL.

Safety notes

  • Telegram MCP Server can read chats and messages, send, schedule, edit, delete, forward, and pin messages, mark chats read, create polls, press inline buttons, manage contacts, manage groups and channels, upload or download media, and update profile settings when write tools are exposed.
  • A Telegram session string has the normal authority of the Telegram account inside the server process; read-only mode limits the MCP tool surface but does not reduce the underlying session authority.
  • The upstream README warns that the PyPI `telegram-mcp` name is owned by a different project, so do not pass Telegram API credentials or session strings to that package.
  • File-path tools are disabled until allowed roots are configured; keep upload and download roots narrow when enabling media or file operations.
  • Require human approval before sending, editing, deleting, forwarding, pinning, reacting, inviting, banning, changing permissions, or updating profile and privacy settings.
  • Use separate Telegram accounts for testing, monitor Telegram rate limits and platform rules, and keep proxies or multi-account routing explicit.

Privacy notes

  • Telegram API IDs, API hashes, session strings, account labels, chat titles, usernames, phone-adjacent identifiers, messages, media, contacts, group membership, profile photos, user status, read receipts, drafts, and folder metadata can be exposed to the MCP client.
  • Chat history and media can contain private conversations, personal data, business records, access links, invite links, documents, photos, voice notes, stickers, GIFs, and user-controlled prompt-injection text.
  • The project includes output sanitization for user-controlled content, but sanitized Telegram content should still be treated as untrusted model input.
  • Store session strings like passwords, keep them out of shell history and shared logs, and revoke sessions if they are exposed.
  • Review MCP transcripts, downloaded media folders, Telegram session files, and proxy logs before sharing or retaining them.

Prerequisites

  • Python 3.10 or newer with `uv` available.
  • A trusted checkout of `https://github.com/chigwell/telegram-mcp`; do not use the unrelated PyPI package with the same distribution name.
  • Telegram API credentials from `my.telegram.org/apps`.
  • A Telegram session string or file-based session generated from the trusted checkout.
  • Review of which accounts, chats, groups, contacts, media paths, and write tools Claude is allowed to access.
  • Start with `TELEGRAM_EXPOSED_TOOLS=read-only` unless the workflow explicitly needs message, account, contact, group, profile, or media mutations.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
30 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
Community-maintained Apache-2.0 MCP server for Telegram via Telethon. The repository explicitly warns that the PyPI `telegram-mcp` name is unrelated, so install from a trusted source checkout or explicit Git URL.
Full copyable content
{
  "mcpServers": {
    "telegram-mcp": {
      "command": "uv",
      "args": ["--directory", "PATH_TO_TELEGRAM_MCP_CHECKOUT", "run", "main.py"],
      "env": {
        "TELEGRAM_API_ID": "YOUR_TELEGRAM_API_ID",
        "TELEGRAM_API_HASH": "YOUR_TELEGRAM_API_HASH",
        "TELEGRAM_SESSION_STRING": "YOUR_TELEGRAM_SESSION_STRING",
        "TELEGRAM_EXPOSED_TOOLS": "read-only"
      }
    }
  }
}

About this resource

Content

Telegram MCP Server connects Claude and other MCP clients to Telegram through Telethon. It exposes tools for Telegram accounts, chats, messages, contacts, media, folders, groups, channels, profile settings, and multi-account routing.

Use it when Claude needs supervised Telegram context or automation, starting with read-only tools for chat review and account inspection before enabling message or account-changing actions.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, license, package manifest, environment template, compatibility entrypoint, sanitizer, install guard, and runtime implementation for current setup and behavior details.

Features

  • List configured Telegram accounts and route calls by account label.
  • List chats, inspect chat metadata, and search message history.
  • Read messages, inspect context, mark chats read, and manage drafts.
  • Send, schedule, edit, delete, forward, pin, unpin, reply to, and react to messages when write tools are exposed.
  • Create polls and inspect or press inline buttons.
  • Manage contacts, blocks, direct chats, and recent interactions.
  • Send, upload, download, and inspect media when allowed file roots are configured.
  • Create and manage groups, channels, admins, bans, permissions, topics, slow mode, invite links, and read receipts.
  • Inspect and update profile, privacy, bot-command, folder, and draft state.
  • Limit exposed MCP tools to read-only mode with TELEGRAM_EXPOSED_TOOLS.

Installation

Clone the trusted repository, install dependencies, and generate a Telegram session string from the checkout before configuring Claude:

{
  "mcpServers": {
    "telegram-mcp": {
      "command": "uv",
      "args": ["--directory", "PATH_TO_TELEGRAM_MCP_CHECKOUT", "run", "main.py"],
      "env": {
        "TELEGRAM_API_ID": "YOUR_TELEGRAM_API_ID",
        "TELEGRAM_API_HASH": "YOUR_TELEGRAM_API_HASH",
        "TELEGRAM_SESSION_STRING": "YOUR_TELEGRAM_SESSION_STRING",
        "TELEGRAM_EXPOSED_TOOLS": "read-only"
      }
    }
  }
}

Claude Code users can add a read-only default configuration with:

claude mcp add telegram-mcp --env TELEGRAM_API_ID=YOUR_TELEGRAM_API_ID --env TELEGRAM_API_HASH=YOUR_TELEGRAM_API_HASH --env TELEGRAM_SESSION_STRING=YOUR_TELEGRAM_SESSION_STRING --env TELEGRAM_EXPOSED_TOOLS=read-only -- uv --directory PATH_TO_TELEGRAM_MCP_CHECKOUT run main.py

Only remove TELEGRAM_EXPOSED_TOOLS=read-only after reviewing the write tools and setting account, media-path, and approval boundaries.

Use Cases

  • Summarize unread Telegram chats for a supervised account.
  • Search chat history for a message, file, link, or conversation context.
  • Draft a response and ask for human approval before sending it manually or via an exposed write tool.
  • Inspect group or channel metadata during community moderation.
  • Export selected contact or chat context for a customer-support workflow.
  • Download approved media into a narrow allowed root for later processing.
  • Manage drafts and folders for a dedicated automation account.

Safety and Privacy

Telegram MCP Server should be treated as account automation. Use a dedicated Telegram account for testing, keep session strings secret, and leave read-only mode enabled unless the workflow truly needs account-changing tools.

Never install this server from the unrelated PyPI package named telegram-mcp. Run it from a trusted checkout or an explicit Git URL, and do not paste real Telegram credentials into package managers, logs, issue comments, or shared model transcripts.

#telegram#messaging#chat#automation#telethon

Source citations

Add this badge to your README

Show that Telegram MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/telegram-mcp-server.svg)](https://heyclau.de/entry/mcp/telegram-mcp-server)

How it compares

Telegram MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field
Telegram MCP Server logoTelegram MCP Server

Telethon-powered MCP server for connecting Claude to Telegram accounts, chats, messages, contacts, media, folders, groups, channels, profile settings, and read-only or full account workflows.

Open dossier
LINE Bot MCP Server logoLINE Bot MCP Server

Official LINE MCP server that connects Claude and other AI agents to the LINE Messaging API for push messages, broadcasts, profile lookup, quotas, follower IDs, and rich-menu management.

Open dossier
AI Game Developer logoAI Game Developer Unity MCP Server

Unity MCP server, plugin, CLI, and skill generator for controlling Unity Editor and runtime projects from MCP clients through built-in game-dev tools.

Open dossier
BuyWhere logoBuyWhere MCP Server

Real-time product search and price comparison across 11M+ products from Singapore, Southeast Asia, and US marketplaces via a remote streamable-HTTP MCP endpoint with API key auth.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1oktofeesh1BuyWhere
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandTelegram MCP Server logoTelegram MCP ServerLINE Bot MCP Server logoLINE Bot MCP ServerAI Game Developer logoAI Game DeveloperBuyWhere logoBuyWhere
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorchigwellLINEIvan MurzakBuyWhere
Added2026-06-062026-06-062026-06-062026-06-26
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Telegram MCP Server can read chats and messages, send, schedule, edit, delete, forward, and pin messages, mark chats read, create polls, press inline buttons, manage contacts, manage groups and channels, upload or download media, and update profile settings when write tools are exposed. A Telegram session string has the normal authority of the Telegram account inside the server process; read-only mode limits the MCP tool surface but does not reduce the underlying session authority. The upstream README warns that the PyPI `telegram-mcp` name is owned by a different project, so do not pass Telegram API credentials or session strings to that package. File-path tools are disabled until allowed roots are configured; keep upload and download roots narrow when enabling media or file operations. Require human approval before sending, editing, deleting, forwarding, pinning, reacting, inviting, banning, changing permissions, or updating profile and privacy settings. Use separate Telegram accounts for testing, monitor Telegram rate limits and platform rules, and keep proxies or multi-account routing explicit.✓LINE Bot MCP Server can push text and flex messages to users, broadcast messages to all followers, retrieve follower IDs, inspect profiles, check message quotas, create rich menus, set default rich menus, cancel defaults, and delete rich menus. Broadcast and rich-menu tools can affect every user following the connected LINE Official Account, so require human approval before running them in production. Push-message tools can contact individual users directly; confirm the target `userId`, message body, and account context before sending. Rich-menu tools can upload generated menu images and change user-facing navigation for the account. Use least-privilege channel tokens where possible, keep test and production LINE accounts separate, and monitor quota consumption. The upstream README marks the project as a preview version for experimental use with potentially incomplete functionality or support.✓AI Game Developer can create, move, copy, modify, and delete Unity assets, scenes, GameObjects, components, scripts, packages, and generated project files. Tools include dynamic C# script execution, C# reflection method lookup and calls, package installation/removal, Unity test execution, editor state changes, play mode control, screenshots, and profiler access. The MCP server supports streamable HTTP and stdio; HTTP deployments should require a bearer token and stay bound to trusted interfaces. Server variables include optional authorization and webhook settings; webhook endpoints can receive tool, prompt, resource, connection, and authorization events. Unity runtime connections can expose compiled game state or in-game behavior to an MCP client, not just editor-only project data. Use source control, backups, tool filtering, and explicit review before allowing destructive tools such as asset deletion, package removal, script execution, or reflection calls.✓Read-only product catalog access by default; no write or delete operations exposed. API key should be stored in the MCP client config or environment, never committed.
Privacy notes✓Telegram API IDs, API hashes, session strings, account labels, chat titles, usernames, phone-adjacent identifiers, messages, media, contacts, group membership, profile photos, user status, read receipts, drafts, and folder metadata can be exposed to the MCP client. Chat history and media can contain private conversations, personal data, business records, access links, invite links, documents, photos, voice notes, stickers, GIFs, and user-controlled prompt-injection text. The project includes output sanitization for user-controlled content, but sanitized Telegram content should still be treated as untrusted model input. Store session strings like passwords, keep them out of shell history and shared logs, and revoke sessions if they are exposed. Review MCP transcripts, downloaded media folders, Telegram session files, and proxy logs before sharing or retaining them.✓Channel access tokens, destination user IDs, follower IDs, profile display names, profile picture URLs, status messages, language, message contents, flex-message JSON, and rich-menu IDs can be exposed to the MCP client. Broadcast prompts, generated messages, user IDs, and profile results may be retained in MCP client logs, terminal history, model context, or chat transcripts. Treat LINE Official Account credentials and recipient identifiers as secrets, and avoid pasting real tokens or user IDs into shared logs. Review LINE platform policies and internal consent requirements before retrieving follower IDs or using AI-generated outbound messages.✓Tool calls may expose Unity project paths, asset names, scene hierarchy, serialized object data, scripts, logs, screenshots, profiler metrics, test output, package metadata, and runtime state. MCP config files and Unity plugin config can contain server URLs, connection modes, bearer tokens, authorization settings, enabled tool IDs, and cloud or local endpoint details. Optional webhooks can receive tool, prompt, resource, connection, authorization, and token-bearing request data. Screenshots from Game View, Scene View, cameras, or isolated GameObjects may include proprietary artwork, level design, UI, debug overlays, or unreleased game content. Generated skills and AI-client configuration files can reveal available tools, project structure, installed packages, and local workflow assumptions.✓BuyWhere API key is sent as a Bearer token in the Authorization header on every request. Search queries are sent to BuyWhere's API to retrieve product data; no third-party analytics or telemetry is included in MCP responses. BuyWhere may log API request metadata (endpoint, timestamp, status) for abuse prevention and billing.
Prerequisites
  • Python 3.10 or newer with `uv` available.
  • A trusted checkout of `https://github.com/chigwell/telegram-mcp`; do not use the unrelated PyPI package with the same distribution name.
  • Telegram API credentials from `my.telegram.org/apps`.
  • A Telegram session string or file-based session generated from the trusted checkout.
  • Node.js 22 or newer for the published npm package.
  • A LINE Official Account with the Messaging API enabled.
  • A LINE channel access token with the permissions needed for the intended tools.
  • A destination user ID when using the default recipient flow for push-message tools.
  • Unity project using Unity 2022.3 or newer for the current package metadata.
  • Unity Hub or a local Unity Editor installation.
  • Node.js 20.19 or newer, or Node.js 22.12 or newer, for `unity-mcp-cli`.
  • An MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, GitHub Copilot, Cline, or another supported client.
  • A BuyWhere API key (free at https://buywhere.ai/api-keys).
  • An MCP client such as Claude Code, Claude Desktop, Cursor, Windsurf, or any MCP-compatible host.
  • Network access to https://api.buywhere.ai.
Install
uv --directory PATH_TO_TELEGRAM_MCP_CHECKOUT run main.py
npx -y @line/line-bot-mcp-server
npm install -g unity-mcp-cli && unity-mcp-cli install-plugin ./MyUnityProject
claude mcp add buywhere --transport http --header "Authorization: Bearer YOUR_BUYWHERE_API_KEY" https://api.buywhere.ai/mcp
Config
Manual-only setup:
claude mcp add telegram-mcp --env TELEGRAM_API_ID=YOUR_TELEGRAM_API_ID --env TELEGRAM_API_HASH=YOUR_TELEGRAM_API_HASH --env TELEGRAM_SESSION_STRING=YOUR_TELEGRAM_SESSION_STRING --env TELEGRAM_EXPOSED_TOOLS=read-only -- uv --directory PATH_TO_TELEGRAM_MCP_CHECKOUT run main.py
Manual-only setup:
claude mcp add line-bot --env CHANNEL_ACCESS_TOKEN=YOUR_CHANNEL_ACCESS_TOKEN -- npx -y @line/line-bot-mcp-server
Manual-only setup:
npm install -g unity-mcp-cli
unity-mcp-cli install-plugin ./MyUnityProject
unity-mcp-cli open ./MyUnityProject
{
  "mcpServers": {
    "buywhere": {
      "type": "http",
      "url": "https://api.buywhere.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BUYWHERE_API_KEY",
        "X-Buywhere-Market": "SG"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Auto Mode Hard-Deny Policies For Safe Automation

Set autoMode.hard_deny rules to block risky actions in auto mode.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Claude Process Automation

Automate business and engineering processes with headless Claude Code, GitHub Actions, and scheduled routines.

Added 8mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JSONbored

Channels and Webhooks into Running Claude Code Sessions

Push messages, alerts, and webhooks into a running Claude Code session with channels, with sender allowlists and enterprise controls.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.