Satismeter

@Satismeter show me all active surveys in our project and their response rates so far

Based on the project configuration, Satismeter returned 3 active surveys: 'Post-Purchase NPS' (247 responses, 18% response rate), 'Feature Feedback - Dashboard' (89 responses, 12% response rate), and 'Onboarding CSAT' (156 responses, 24% response rate). The Post-Purchase survey is set to trigger 7 days after checkout, while the Dashboard survey appears after 3 feature interactions. All three are currently collecting responses.

This example uses the List Surveys tool to fetch campaign metadata. The MCP returns survey configuration and basic metrics, but detailed response analytics (sentiment breakdowns, verbatim comments) typically require separate API calls or dashboard access. Requires a valid project ID in your Satismeter account.

@Satismeter add these three emails to the unsubscribe list: user1@example.com, user2@example.com, user3@example.com

Successfully updated the unsubscribe list for your project. The three email addresses have been added and will no longer receive survey invitations from any active campaigns. Satismeter confirmed the update with no errors. Note that this action affects all surveys in the project — these users won't see the Post-Purchase NPS, Feature Feedback, or Onboarding CSAT surveys going forward.

This uses the Update Unsubscribed Emails tool, which performs a bulk write operation. The side-effect is immediate and project-wide: unsubscribed users are excluded from all current and future surveys. This cannot be undone via the MCP — you'd need to manually remove emails from the unsubscribe list in the Satismeter dashboard or API.

@Satismeter generate the embed code for our onboarding survey and explain where I should place it in our React app

Here's the JavaScript snippet for your Onboarding CSAT survey (write key: sk_xxxxxx). The AI recommends placing this in your main App.js or layout component, wrapped in a useEffect hook that fires after successful user authentication. The snippet initializes Satismeter with your project settings and will display the survey according to the targeting rules you configured (e.g., after 3 days of account activity). Make sure to replace the placeholder user traits with actual user data from your auth context.

This example combines the Embed Survey tool with the AI's implementation guidance. The MCP generates the raw JavaScript snippet, but the AI adds context about React integration patterns. The embed code requires a valid write key from your Satismeter project settings. Survey targeting and display logic are controlled in the Satismeter dashboard, not in the embed code itself.

When Satismeter MCP saves setup time for product teams

A 5-person SaaS team ships a new onboarding flow and wants to measure NPS at day 7. The PM opens Switchy, asks the agent to embed a survey targeting users who completed setup in the last week, and gets back the javascript snippet in 30 seconds. The MCP pulls the project config, generates the embed code with the right triggers, and drops it straight into the team's shared context. This works when your survey logic is simple (one trigger, one audience segment). If you're running A/B tests across multiple cohorts or need complex branching, you'll still configure that in Satismeter's UI first—the MCP just handles the retrieval and embed generation. For teams running 2-4 standard NPS or CSAT campaigns, this cuts the setup-to-deploy cycle from 20 minutes to under 2.

Using this MCP to clean survey opt-out lists

A 3-person customer success team at a B2B startup notices their survey response rate dropped from 18% to 9% over six months. They suspect their unsubscribe list is bloated with churned users or test accounts. The CS lead asks Switchy to pull the full unsubscribe list, cross-reference it against their CRM export, and flag emails that no longer exist in the customer base. The MCP's Get Unsubscribed Emails tool returns the raw list; the agent does the diff and proposes a bulk update. This scenario works if your unsubscribe list is under 5,000 emails and you have a clean CRM export to compare against. Beyond that scale, you're better off scripting the reconciliation directly against Satismeter's API. For small CS teams doing quarterly hygiene passes, this turns a 2-hour spreadsheet task into a 10-minute conversation.

When this MCP helps support reps surface feedback fast

A 6-person support team gets an escalation from a customer who mentioned 'survey feedback' in their ticket but didn't include details. The support rep opens Switchy, asks the agent to list recent surveys and pull responses for that user's email. The MCP's List Surveys and List Users tools return the campaign history and user metadata in one query. The rep sees the customer gave a 3/10 score on the last CSAT survey two weeks ago, copies the verbatim into the ticket, and escalates to product. This works when your support team fields 10-30 tickets a day that reference survey data and you don't want to train everyone on Satismeter's dashboard. If your volume is higher or you need real-time alerting on low scores, integrate Satismeter webhooks into your ticketing system instead. For small support orgs doing ad-hoc lookups, this MCP keeps context in Switchy without adding another login.