Customer Thermometer MCP server
MCP server for Customer Thermometer's customer feedback / NPS survey API.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Customer Thermometer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Customer Thermometer tools
No tool declarations could be read from the package source. They show once the server is installed.
How Customer Thermometer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 33% of 48,243 servers
Release history: 2 versions in the registry since 2026-09-20, latest 2026-10-22, typically one every 32 days.
Install Customer Thermometer in Claude Code, Cursor or VS Code
claude mcp add customer-thermometer-mcp -- docker run -i --rm ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.5
What the publisher says
From the Customer Thermometer repository's README, as published. We do not edit it. Read it on GitHub
Customer Thermometer MCP Server
MCP server for Customer Thermometer's customer feedback / NPS survey API - thermometers, recipient lists, sending, and reporting, for AI assistants and the WYRE Conduit gateway.
Authentication
Customer Thermometer authenticates with a single static API key, generated from your account's Integration settings. Either a "Super API key" (full account access) or a narrower "sub-API key" works with this connector.
Configuration
Tools
Lists
- customerthermometergetthermometers - list all survey templates (Thermometers) on the account.
- customerthermometergetrecipient_lists - list all recipient lists on the account.
Recipients
- customerthermometeraddrecipienttolist - add a recipient to a list.
- customerthermometerunsubscriberecipient - add an email address to the account's unsubscribe list.
Sending
- customerthermometersendemail - send a single Email Thermometer survey to one recipient.
- customerthermometergetcredits - remaining Thermometer send credits on the account.
Reporting
- customerthermometergetnps_value - Net Promoter Score, optionally filtered by blast/date range.
- customerthermometergethappiness_value - Happiness Factor percentage, optionally filtered by blast/date range.
- customerthermometergetblast_results - raw survey responses, optionally filtered by temperature/blast/date range.
- customerthermometergetcomments - free-text comments left with responses, optionally filtered by temperature/blast/date range.
The read endpoints that return XML (getThermometers, getRecipientLists, getBlastResults, getComments) are parsed generically rather than mapped to a hand-written schema - the vendor's API documentation does not publish the element names for these responses, so the parsed structure is passed straight through instead of risking a schema that doesn't match the live response.
Scope
This is a v1 surface covering the core survey workflow: listing thermometers/lists, adding and unsubscribing recipients, sending surveys, and reading NPS/happiness/response/comment reports. Explicitly out of scope for now: logResponse and deleteResponse - destructive, lower-value endpoints that mutate or discard existing response data. They can be added as a follow-up if there's demand.
Development
npm install
npm run build
npm test
npm run lint # tsc --noEmitDocker
docker build -t customer-thermometer-mcp .
docker run -p 8080:8080 -e CUSTOMERTHERMOMETER_API_KEY=... customer-thermometer-mcpNothing above is checked by us. What we check is on the safety report.
Customer Thermometer: common questions
- Is Customer Thermometer MCP server safe?
- Mostly: it is graded B (70/100). Read the Customer Thermometer safety report
- How do I install Customer Thermometer?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Customer Thermometer need an API key?
- Yes. The registry entry asks for
CUSTOMERTHERMOMETER_API_KEY. - Is Customer Thermometer maintained?
- The last commit was 23 days ago (2026-10-13). The latest release is v1.0.5.