Notification for Telegram
The “Notification for Telegram” plugin for WordPress is a tool that allows you to send notifications and messages to a Telegram channel, group or user/s when specific events occur on your WordPress site. This plugin is useful for monitoring critical events on your site, such as new comments, new user registrations, publishing activities, New forms sent,Woocommerce and Surecart orders, cart and lowstock, Mailchimp and more, by sending notifications directly to a Telegram channel or group or user/s of your choice. It also offers a shortcode to send Telegram notifications on every page of your website or in your code. Receive Telegram messages notification when: When receive a new order in Woocommerce. When a Woocommerce order change status. When receive a new order in Surecart. Every event captured by WP Activity Log plugin You can also send messages directly from the shell using WP-CLI with ‘wp telegram send “Backup complete”‘ New field in Woocommerce checkout page let customers add the own telegram nickname Low Stock Product notifications when a product is low stock conditions. Shows Telegram Nick link in admin order details page when present When receive new forms (supports Elementor Pro Form, WPForm , CF7 and Ninjaform) When new user subscribes or unsubscribes to mailchimp. MC4WP integration When new user registers. Helps identify unauthorized or suspicious registrations. When users login or fail login. When new comment is posted. When someone adds or remove a product in the Woocommerce cart. When a new Pending posts is received. (works with any post type) Say function to speak to make the bot say Something to the people Cron job detect and notify when Plugins & Core need to update. Send custom message with Shortcode anywhere in your WP. Should Work on Multisite You can enable/disable every notification in the Plugin settings page. To configure the plugin, you need a valid Telegram API token. Its easy to get starting a Telegram Bot. You can learn about obtaining tokens and generating new ones in Setup Guide Setup Wizard: a guided 3-step popup appears automatically on first install to help you configure your Telegram bot token and Chat ID A complete step-by-step guide is available here: View the full documentation To get your Bot Token, you can refer to one of these resources: Official Telegram documentation Step-by-step guide on Medium To get your Chat ID, you need at least one recipient ID. You can retrieve it using one of these bots directly in Telegram: @get_id_bot — send /start and it will reply with your personal Chat ID @RawDataBot — send any message and it will return your full account info including your ID For Channel and Group Chatid settings see the FAQ section. Once You got the 2 fields save the configuration and try the “TEST” button .. you should receive a message in you telegram : “WOW IT WORKS” !! If not, check token and chatid fields again for the correct values. this plugin is relying on a 3rd party service to geolocate the Ip address https://ip-api.com/ https://ip-api.com/docs/legal to see the services’ a terms of use and/or privacy policies AI & MCP Compatible This plugin supports the WordPress Abilities API and is compatible with MCP (Model Context Protocol) — the standard that allows AI agents like Claude, ChatGPT, and others to interact with WordPress autonomously. If the Abilities API and MCP Adapter plugins are installed, any authorized AI agent can automatically discover and use the Send Telegram Message ability — no extra configuration needed. What an AI can do with this plugin: * Send a Telegram message with custom text * Add an inline button with label and URL * Override the default chat ID Requirements for MCP WordPress 7.0+ (Abilities API built-in) Plugin: MCP Adapter Enable “AI / MCP” in the plugin settings WordPress 6.9 compatibility WordPress 6.9+ Plugin: Abilities API Plugin: MCP Adapter WP-CLI support Send Telegram messages directly from the shell using wp nftb send wp telegram send “Hide WORLD” MESSAGES TRANSLATION To translate Telegram messages, use WPML or Loco Translate. All notification strings are now translatable. Go to Loco Translate → Plugins → Notification for Telegram to add your translations. For WPML, ensure String Translation is enabled to modify notification texts. ACTION HOOK for third-party Plugin Notification for Telegram (version > 3.5.1) exposes a dedicated action hook so any third-party plugin can send messages without calling internal functions directly. Basic usage: do_action( ‘nftb_send_message’, ‘Your message here’ ); Look FAQ Section for more esamples. SHORTCODE EXAMPLE [telegram_mess message="Im so happy" chatids="0000000," token="000000000:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA" showsitename="1" showip="1" showcity="1" ] Look FAQ Section for more esamples. Suggestions for new notifications, hooks, and plugin integrations are always welcome!
StrifeBridge MCP
StrifeBridge MCP turns your WordPress site into an MCP (Model Context Protocol) endpoint that AI assistants like Claude can connect to directly. Instead of describing a change to an AI and then applying it yourself, you ask and it happens. Want to add a blog post? Ask Claude. Need to update a menu item? Ask Claude. Wondering which pages are missing SEO metadata? Ask Claude to check and fix them. StrifeBridge MCP exposes a structured, authenticated REST API and MCP server inside your WordPress install. AI assistants that support MCP (ChatGPT, Claude.ai, Claude Desktop, Gemini, Cursor, Windsurf, and any MCP-capable agent framework) can connect to it and perform tasks across your site through natural language. Connections use OAuth 2.1 and act as a real WordPress account, so an assistant is held to that account’s permissions. What you can do Create, update, and delete posts, pages, and custom post types Upload files to the media library and manage attachments Read and write WordPress options, with a security blacklist for sensitive keys Manage navigation menus, taxonomy terms, and widgets List, activate, deactivate, and delete plugins List users and inspect their roles Get site info, flush rewrite rules See and control what the AI does Every tool call is recorded in an activity log — what ran, whether it worked, and where the request came from, including refused calls and failed sign-in attempts. The Settings screen shows recent activity at a glance. Safe Mode adds guardrails on top of the per-tool-group toggles: Never publish — new posts stay drafts, and updates cannot publish them Trash instead of delete — deletions stay recoverable Read-only mode — the AI can look but not touch How it works Install and activate the plugin Go to Settings and copy your Server URL Paste it into your AI assistant as a custom MCP connector The assistant sends you back to WordPress to sign in and approve the connection Ask the assistant to do things on your site No middleware, no third-party relay service. Every request goes from your AI assistant directly to your own WordPress site. You own the endpoint, you own the token, and you can revoke access at any time from Settings. Compatible with ChatGPT — via OAuth Google Gemini — via OAuth Claude.ai (web and desktop), and Claude Code Cursor Windsurf Any MCP-capable agent framework ChatGPT and Gemini require OAuth, which arrived in version 3.0.0. The others accept either OAuth or the legacy token. Security StrifeBridge MCP was designed with security as a first-class concern: OAuth 2.1 with mandatory PKCE (S256 only; the plain method is refused), single-use 60-second authorization codes, exact-match redirect URIs, and rotating refresh tokens Tokens, authorization codes, and client secrets are stored only as hashes and compared in constant time with hash_equals() Every connection is bound to a WordPress account and subject to that account’s capabilities, and can be revoked individually from Settings WordPress secret keys, auth salts, and the plugin’s own token are blacklisted from the options API Emergency Lockdown button in Settings disables the entire API with one click Every tool group (posts, media, menus, etc.) can be individually toggled off from Settings The plugin includes no outbound network calls, no analytics, and no tracking Compatibility with self-hosted WordPress StrifeBridge MCP works on any self-hosted WordPress installation running WordPress 5.6 or higher. WordPress.com and WordPress Multisite are not currently supported. Extending StrifeBridge MCP StrifeBridge MCP exposes extension hooks that let add-on plugins register additional MCP tools without modifying the core plugin. Developers can hook into sbmcp_register_rest_routes, sbmcp_mcp_tools, sbmcp_mcp_tool_call, sbmcp_tool_groups, and sbmcp_admin_after_settings to add routes, tools, admin UI, and tool groups. This is how separately distributed add-ons extend the plugin with features like file editing, database queries, and user management. Privacy StrifeBridge MCP keeps an activity log in your own WordPress database, in a table named {prefix}sbmcp_audit_log. Each entry records the time of the request, the name of the tool that ran, a short sanitized summary of what it acted on, whether the call succeeded, failed, or was refused, and — unless you turn it off — the IP address the request came from. Nothing leaves your site. The log is local to your database. The plugin makes no outbound network calls and sends no analytics or telemetry anywhere. No content or secrets are stored. Argument summaries are allowlisted per tool, so option values, post content, widget settings, uploaded file data, and API tokens are never written to the log. A tool the plugin does not recognize records no arguments at all. IP logging is optional. “Log IP addresses” under Settings → StrifeBridge MCP → Safety is on by default and can be switched off, after which new entries store no address. Entries already recorded keep the addresses they were written with; deleting those is a matter of waiting for them to be pruned, or clearing the table. Entries are pruned automatically. A daily scheduled task keeps the free version to a rolling window of 30 days or 1000 entries, whichever comes first. Older entries are deleted permanently. Everything is removed on uninstall. Deleting the plugin through the WordPress admin drops the log table and removes every option the plugin created. Deactivating alone leaves the log in place, so it survives a temporary deactivation. If your site is subject to GDPR or similar regulation, note that IP addresses are personal data. Either switch IP logging off, or account for this log in your own privacy policy and retention practices.
