# Engagespot MCP

> Engagespot manages multi-channel user communications. It lets your AI agent trigger complex workflows—like sending a new order email, updating SMS preferences, or creating a user profile—across Email, SMS, and in-app messages directly from conversation.

## Overview
- **Category:** communication-messaging
- **Price:** Free
- **Tags:** notifications, multi-channel, user-engagement, workflow-automation, messaging-api

## Description

Use this MCP to orchestrate all your customer notifications through natural conversation. You can build sophisticated communication flows that hit multiple channels: email, text message, and push notification. For example, you don't have to manually send an alert; you just tell your agent to trigger a 'new order' workflow for a specific user ID, and the system handles everything else. It also keeps your user data clean by letting you create new profiles or update existing ones in one go. The whole thing works as a communication orchestrator, ensuring users get exactly the right message at the right time, whether that means updating their notification settings or clearing out old messages from their inbox. This catalog of tools is available through Vinkius, giving your agent access to hundreds of other services alongside Engagespot.

## Tools

### cancel_workflow_run
Stops a running notification workflow before it sends unwanted messages.

### create_or_update_user
Adds a new user to the system or changes details for an existing profile.

### delete_all_notifications
Wipes out every single notification record associated with the authenticated user.

### delete_notification
Removes one specific notification from a user's history using its unique ID.

### delete_user
Permanently removes a user account from the system workspace.

### get_preferences
Retrieves all notification preferences for the authenticated user across different channels.

### list_notifications
Fetches a list of recent notifications that have been sent to the authenticated user.

### send_notification
Triggers an entire communication workflow, delivering a message using unique data and identifiers.

### update_preferences
Changes notification preferences for the authenticated user across various categories.

## Prompt Examples

**Prompt:** 
```
Send a 'new_order' notification to user_99 with data {"orderId": "12345"}.
```

**Response:** 
```
I've triggered the 'new_order' workflow for user_99. The notification has been queued for delivery with the provided order data.
```

**Prompt:** 
```
Update user 'dev_user_01' with email 'dev@company.com' and first name 'Alice'.
```

**Response:** 
```
User 'dev_user_01' has been successfully updated. The profile now reflects the new email and first name in the Engagespot database.
```

**Prompt:** 
```
List my recent notifications and then clear my inbox.
```

**Response:** 
```
I've retrieved your notifications. You had 3 unread messages. As requested, I have now cleared your entire inbox using the delete all command.
```

## Capabilities

### Send Multi-Channel Notifications
Trigger complex workflows that send alerts via email, SMS, or in-app push messages.

### Manage User Profiles
Create new user accounts or modify details for existing users within the system.

### Adjust Notification Settings
Read what a specific user prefers to receive, and then update those preferences across various communication channels.

### Audit User Communication History
Pull lists of past notifications for any user or completely wipe out their notification history.

## Use Cases

### Onboarding a New Enterprise Client
A Customer Success Manager needs to onboard a new client. Instead of logging into three different tools, they ask their agent: 'Create user X and send them the welcome workflow.' The agent uses `create_or_update_user` followed by `send_notification`, completing the entire process in one go.

### Debugging a Messaging Failure
A Product Engineer finds that some users aren't getting push notifications. They ask their agent to use `get_preferences` for user Y and check the last 10 messages using `list_notifications`, pinpointing exactly where the communication flow broke.

### Handling a User Account Change
A DevOps team member updates an old customer's details. They use `create_or_update_user` to change the email and then immediately run `update_preferences` so the system knows where to send future alerts.

### Cleaning up Stale Data
A team needs to remove a user who left the company. They first use `delete_user`, confirm all their notifications are cleared using `delete_all_notifications`, and then cancel any active workflows with `cancel_workflow_run`.

## Benefits

- Eliminate manual API calls. You can test full notification logic and user profile syncing directly through conversation, saving hours of boilerplate coding time for Product Engineers.
- Maintain a clean record of user data by using the tools to create or update profiles immediately after a customer service interaction, ensuring your backend stays synchronized.
- Handle complex communications with confidence. Instead of piecing together multiple API calls, you trigger one workflow and know that every channel—SMS, email, push—gets the message it needs.
- Improve user data hygiene by easily listing or deleting notifications using `list_notifications` or clearing the whole inbox with `delete_all_notifications`. No more messy manual database cleanup.
- Quickly manage compliance and communication rules. You can pull current settings with `get_preferences` or make a mass change using `update_preferences` when required.

## How It Works

The bottom line is that you treat your entire notification infrastructure like a single chat command.

1. Subscribe to the MCP and provide your Engagespot API Key, Secret, and Target User ID.
2. Tell your AI agent what needs to happen—for instance, 'Send a welcome email to user 456 with this data.'
3. The system executes the full workflow automatically, delivering the message across all required channels.

## Frequently Asked Questions

**How do I check a user's notification history with Engagespot MCP?**
You use the `list_notifications` tool. This command retrieves a record of all messages sent to the authenticated user, allowing you to audit their communication history.

**Can I delete specific notifications using Engagespot MCP?**
Yes, that's what the `delete_notification` tool does. You just need to provide the unique ID of the message you want removed from the user's history.

**What if a workflow fails midway with Engagespot MCP?**
If an active communication flow is running and needs stopping, use `cancel_workflow_run`. This prevents further messages from being sent out by the system.

**How do I update user data using Engagespot MCP?**
You run the `create_or_update_user` tool. This function is smart enough to either build a brand new profile or simply overwrite specific details on an existing one.

**Does Engagespot MCP handle multi-channel sending?**
Absolutely. The `send_notification` tool allows you to trigger complex workflows that send messages across multiple channels, like combining an email with an SMS alert.