# Novu MCP for AI Agents AI Agent Connect > Novu MCP lets you manage your entire multi-channel notification infrastructure directly through your AI agent. You can trigger alerts across Email, SMS, Push, and Chat, manage subscriber databases, and update user preferences without leaving your workspace. It handles the heavy lifting of notification logic while you stay focused on building your product. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_Gc629xN4mo0qmuVJaVaxK1NHXyH1KKUxILlM77rl/ai-agent-connect - **Tags:** notification-infrastructure, multi-channel, subscriber-management, event-triggering, push-notifications, workflow-automation ## Description Managing notifications across different channels usually feels like a chore. You're constantly jumping between your code editor and a dashboard just to see if a welcome email actually went out or to check if a specific user opted out of SMS alerts. This Connector changes that by bringing your Novu account directly into your AI client. Instead of manual testing or hunting through logs, you can just tell your agent to fire off a test broadcast or find a specific subscriber to see what their settings look like. It's like having a communications engineer sitting right next to you, handling the nuances of multi-channel delivery while you keep moving. When you're looking for a way to organize your notification logic, you'll find that having this in the Vinkius catalog makes it much easier to keep your communication stack consistent. You get to handle complex workflows, like delayed digests or bulk updates, using plain language instead of wrestling with nested JSON payloads in a separate tab. ## Tools ### update_topic Modifies the settings of a specific topic. Use this to change the rules for a specific alert category. ### bulk_update_subscriber_preferences Updates preferences for multiple subscribers at once. Use this to perform large scale preference changes. ### create_integration Sets up a new integration for your notification channels. Use this to add new providers to your stack. ### create_layout Builds a new layout for your notification content. This helps you structure how messages appear to users. ### create_subscriber Adds a new subscriber to your database. This is the first step in getting a user into your communication flow. ### create_topic_subscriptions Enrolls subscribers into a specific topic. This helps group users by their interests or needs. ### create_topic Sets up a new topic for categorized notifications. Use this to organize your communication themes. ### create_workflow Builds a new notification workflow from scratch. Use this to define the logic for your alerts. ### delete_integration Removes an existing integration from your account. Use this to clean up unused notification providers. ### delete_message Deletes a specific message from your history. This helps in keeping your logs clean during testing. ### delete_subscriber_credentials Wipes the credentials for a specific subscriber. Use this to reset user access or clear old data. ### delete_subscriber Removes a subscriber from your database. Use this to clean up your subscriber list. ### delete_topic_subscriptions Unenrolls subscribers from a specific topic. This is useful for removing users from specific alerts. ### delete_topic Removes a topic from your account. Use this to delete old communication categories. ### get_environment_variable_usage Shows how much an environment variable is being used. Use this to monitor your configuration health. ### get_subscriber_preferences Shows the specific notification settings for a subscriber. Use this to check what a user has opted into. ### get_subscriber Pulls the full data for a subscriber using their unique ID. Use this to inspect a user's full profile. ### get_topic_subscription Retrieves the details of a specific topic subscription. This helps you see exactly what a user is receiving. ### list_integrations Shows all your current integrations. Use this to see which notification channels are active. ### list_messages Lists your recent messages for review. Use this to check the history of sent notifications. ### list_topic_subscriptions Shows all subscriptions for a given topic. Use this to see how many users are enrolled in a specific category. ### search_subscribers Finds subscribers based on your search criteria. Use this to quickly locate a user by email or name. ### set_primary_integration Marks a specific integration as your main channel. Use this to set your default notification method. ### trigger_broadcast Sends a notification to every subscriber in your database. Use this for company-wide announcements. ### trigger_bulk_event Fires multiple events in a single request to save time. Use this to trigger many notifications at once. ### trigger_event Sends a notification to one or more specific subscribers. Use this to fire off targeted alerts. ### update_environment_variable Modifies an existing environment variable. Use this to change your configuration on the fly. ### update_integration Changes the settings of an existing integration. Use this to update your provider credentials or settings. ### update_subscriber_credentials Refreshes the credentials for a subscriber. Use this to keep user access up to date. ### update_subscriber_preference Changes a specific preference for a subscriber. Use this to update what a user wants to receive. ### update_subscriber Updates the core info for an existing subscriber. Use this to change a user's name or email in your system. ### upsert_subscriber_credentials Creates or updates subscriber credentials in one step. Use this to handle new users or update existing ones. ### cancel_trigger Stops active or pending workflows like digests or delayed notifications. This is useful when you need to halt a message before it sends. ### check_topic_subscriber Verifies if a specific subscriber is enrolled in a particular topic. Use this to check user permissions quickly. ### create_environment_variable Adds a new environment variable to your Novu setup. This helps keep your configuration organized. ### delete_messages_by_transaction Removes all messages associated with a specific transaction ID. This is great for clearing out bulk test data. ### get_topic Fetches the details of a topic based on its key. Use this to verify the settings of a specific alert category. ### list_environment_variables Shows all environment variables in your account. Use this to see your global configuration at a glance. ### list_active_integrations Shows which integrations are currently active. Use this to verify your notification channels are live. ## Prompt Examples **Prompt:** ``` I need to send a test welcome message to a new user named John Doe with the email john@example.com. Can you trigger the welcome flow? ``` **Response:** ``` I've initiated the welcome workflow for the new subscriber. * **Subscriber:** John Doe (john@example.com) * **Action:** Triggered 'welcome-onboarding' * **Status:** Success * **Transaction ID:** `tx_998877` ``` **Prompt:** ``` Can you find the subscriber with the email support@company.com and tell me if they're subscribed to our 'billing' topic? ``` **Response:** ``` I found the subscriber you're looking for. * **Name:** Support Team * **ID:** `sub_5544` * **Topic Status:** Yes, they are currently subscribed to the **billing** topic. * **Preferences:** They have opted into Email and Push notifications. ``` **Prompt:** ``` We have a delayed digest that's stuck. Can you cancel the one with transaction ID tx_abc123? ``` **Response:** ``` I've successfully cancelled the workflow for transaction `tx_abc123`. The delayed digest will no longer be sent to your subscribers. ``` ## Capabilities ### Trigger multi-channel alerts Send notifications across Email, SMS, Push, and Chat in a single action. ### Manage subscriber databases Create, search, and update user records instantly to keep your data clean. ### Control user preferences View and modify what specific users want to receive to ensure compliance. ### Cancel pending workflows Stop active digests or delayed notifications before they hit your users. ### Handle multi-tenant contexts Manage notification settings for different clients or environments easily. ## Use Cases ### Testing a welcome flow A developer wants to test a welcome message. They ask the agent to trigger_event for a test user and then get_subscriber to check the payload. ### Running a company-wide blast A growth lead needs to send a blast. They ask the agent to trigger_broadcast to all users and then list_messages to verify the count. ### Checking user opt-outs A product manager needs to check opt-outs. They ask the agent to search_subscribers for an email and get_subscriber_preferences to see their status. ### Stopping a stuck digest A developer needs to stop a stuck digest. They use cancel_trigger with a transaction ID to stop a delayed message from sending. ## Benefits - Stop switching tabs by managing your entire notification infrastructure within your AI client. - Send multi-channel alerts using trigger_event and trigger_broadcast without manual API calls. - Quickly find and update users with search_subscribers and update_subscriber to maintain clean data. - Handle complex logic like cancel_trigger to stop delayed messages before they hit your users. - Manage multi-tenant environments by using list_environment_variables to keep settings organized. - Verify user opt-outs instantly with get_subscriber_preferences to ensure compliance. ## How It Works The bottom line is you get a hands-on way to manage your entire notification stack without ever opening a separate dashboard. 1. Subscribe to the Novu MCP within your preferred AI client. 2. Enter your Novu Secret Key to establish the connection. 3. Start managing your notification flows and subscribers using natural language. ## Frequently Asked Questions **Can the Novu MCP send notifications to multiple channels at once?** Yes. You can trigger messages across Email, SMS, Push, and Chat simultaneously using the same commands. **How does the Novu MCP help with subscriber management?** It lets your AI agent find, create, and update subscriber records instantly. You can also check specific preferences to ensure you're following user opt-out rules. **Can I use the Novu MCP to stop a notification that's already scheduled?** Yes, you can use it to cancel active or pending workflows, such as delayed digests, using their specific transaction IDs. **Is the Novu MCP good for multi-tenant apps?** It's built for it. You can manage different tenant contexts and environment variables to keep your notification settings separate for different clients. **How do I update preferences for a large group of users using the Novu MCP?** You can use the bulk update feature to change preferences for many subscribers at once, which is much faster than doing it individually. **Can the Novu MCP help me test my notification payloads?** Definitely. You can ask your AI agent to trigger events with specific payloads and then check the results without needing to write manual API requests. **Can I send a notification to all my subscribers at once?** Yes! Use the `trigger_broadcast` tool with your workflow name. This will initiate a notification event for every existing subscriber in your Novu environment. **How do I find a subscriber if I only have their email address?** You can use the `search_subscribers` tool and provide the email as a parameter. The agent will return the subscriber's full profile, including their unique `subscriberId`. **Is it possible to stop a notification that is currently in a 'delay' or 'digest' state?** Yes. By using the `cancel_trigger` tool with the corresponding `transactionId`, you can halt any active or pending workflow execution before it reaches the final delivery.