"Traditional Chinese Medicine or TCM Overview" matching MCP servers:

Enables AI assistants to manage Telegram files, messages, and dialogs directly via MTProto, supporting upload, download, search, forwarding, and storage overview operations.

Native MCP Overview RongCloud Native MCP is a lightweight RongCloud IM service wrapper based on the MCP (Model Control Protocol) protocol. By directly wrapping the high-performance Rust IM SDK, it provides a simple and efficient instant messaging solution for client-side or local applications

A Model Context Protocol server that bridges Microsoft Teams with MCP-compatible clients (LLMs, agentic frameworks, CLI), enabling chat integration, message search, and event streaming without traditional REST API endpoints.

Enables AI agents to notify users via Telegram or Discord when tasks complete, then wait for and receive the user's reply as the next instruction within the same session.

Enables remote control of the Cursor AI agent via chat platforms like GitHub Issues or Telegram, allowing users to start sessions and receive summaries and prompts in a chat thread.

Enables AI assistants to draft content such as PR descriptions, tickets, or messages, with a review window for live preview, editing, and approval before submission.

Enables AI assistants to interact with GroupMe conversations through agentic tools, including a unified inbox for groups and DMs, reading and searching message history, viewing highlights, sending messages, and liking or unliking messages.

Discover and connect your agents with other agents via A2A protocol. Share resources for free or fee.

A send-only Telegram MCP server enabling agents to message you or named contacts via a Telegram bot, with audit copies to the owner.

Scans suspicious messages, URLs, and text for scams inside any MCP-compatible AI assistant. No signup or API key needed for anonymous use.

MCP server for pushing scheduled or triggered messages to personal WeChat via ClawBot, using WorkBuddy connector and WeChat iLink API.

Enables AI coding agents in different harnesses, projects, or machines to share encrypted peer-to-peer rooms and exchange messages directly, without any central server or account.

The official MCP server for Nahook. Manage webhook endpoints, inspect deliveries and delivery attempts, retry failed deliveries, and list environments — directly from Claude, Cursor, Cline, or any MCP-compatible client.

Enables AI agents to send push alerts to your phone via Blipr, useful for notifying when tasks complete, builds break, or approvals are needed.

Enables Claude chats to communicate across machines or sessions via shared encrypted rooms, with tools to create, join, send, read, wait, search, and delete room messages.

An email MCP server that lets Claude or any MCP client search, read and draft mail via IMAP, treating every message as untrusted input. It prioritizes safety with plain-text-only bodies, disabled sending until an allowlist is set, and no bcc support.

Human-in-the-loop approval inbox for AI agents: an agent proposes an action (send email, post comment, run a command), a human approves, rejects, or edits it from a web, mobile, or Slack/Discord/Telegram inbox, and the agent only runs on approval. Full audit trail, self-hostable (MIT).

Enables agents to send tasks and notifications to phones, wait for replies, append follow-ups, cancel mistakes, and query or search the full history of tasks, answers, and submissions as a knowledge base.

LinkedIn outreach from Claude, Cursor or ChatGPT: finds the right people, writes to them in your own voice, follows up and handles replies. For sales prospecting, recruiting, user-interview recruitment, job search and investor or partner outreach; campaigns stay drafts until you launch them.

Use a fmsg address for a fmsg host. Tools for inbox, threads, send and reply, reactions, attachments, delivery status and wait-for-message over the host's WebSocket so agents can hold conversations with people or other agents. Runs over stdio locally or as a Streamable HTTP endpoint where each user authenticates with their own fmsg API key.