Customer Thermometer MCP Server
This MCP server exposes Customer Thermometer survey/NPS operations so AI assistants can manage recipients, send surveys, and read feedback reports.
List survey templates (Thermometers) and recipient lists.
Add recipients to lists and unsubscribe email addresses.
Send a single Email Thermometer survey to a recipient.
Check remaining survey send credits.
Retrieve Net Promoter Score and Happiness Factor, optionally filtered by blast or date range.
Retrieve raw survey responses and free-text comments, optionally filtered by temperature, blast, or date range.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Customer Thermometer MCP Server What's our Net Promoter Score for the last 30 days?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: @indica-facil/mcp-chatwoot
Configuration
Copy .env.example and set the variables below.
Env var | Description |
| API key issued by Customer Thermometer. Used by stdio and by HTTP when |
|
|
|
|
| Required for HTTP. HMAC key checked against |
| Set to exactly |
| Bind address when |
| HTTP port. Defaults to |
|
|
/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
HTTP authentication
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The header value is t=<unix seconds>,v1=<hex>. <hex> is HMAC-SHA256 of the literal string t=<unix seconds> (the same t= prefix and timestamp), keyed with CONDUIT_S2S_SECRET, encoded as 64 lowercase hex characters. The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before vendor credentials are read.
In AUTH_MODE=gateway, /mcp also requires X-CustomerThermometer-Api-Key. That header is the only credential source for the request. A request missing it returns 401 and does not fall back to CUSTOMERTHERMOMETER_API_KEY.
Request limits
HTTP request bodies are capped at 256 KiB (262144 bytes). After the
X-Gateway-S2Scheck passes, aContent-Lengthabove the cap returns 413 with a JSON-RPC error; bodies withoutContent-Lengthare capped by the MCP SDK transport. Unauthenticated requests still get 401 first.tools/callarguments are capped at 10,000 elements (every array item and object key at any depth). Larger inputs return anisErrortool result and are never dispatched.
These limits address CVE-2026-111768 / GHSA-46jr-4wx8-v453 (memory exhaustion during validation) and GHSA-f897-62hf-6gxq (no request body / batch cap).
Tools
Lists
customerthermometer_get_thermometers- list all survey templates (Thermometers) on the account.customerthermometer_get_recipient_lists- list all recipient lists on the account.
Recipients
customerthermometer_add_recipient_to_list- add a recipient to a list.customerthermometer_unsubscribe_recipient- add an email address to the account's unsubscribe list.
Sending
customerthermometer_send_email- send a single Email Thermometer survey to one recipient.customerthermometer_get_credits- remaining Thermometer send credits on the account.
Reporting
customerthermometer_get_nps_value- Net Promoter Score, optionally filtered by blast/date range.customerthermometer_get_happiness_value- Happiness Factor percentage, optionally filtered by blast/date range.customerthermometer_get_blast_results- raw survey responses, optionally filtered by temperature/blast/date range.customerthermometer_get_comments- 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
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode the API key arrives on each request as X-CustomerThermometer-Api-Key; it is not read from the environment. Every /mcp request must also include a valid X-Gateway-S2S signature (see HTTP authentication).
docker build -t customer-thermometer-mcp .
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-p 127.0.0.1:8080:8080 \
customer-thermometer-mcpCompose refuses to start when CONDUIT_S2S_SECRET is unset, defaults AUTH_MODE to gateway, publishes 127.0.0.1:8080:8080, and does not set CUSTOMERTHERMOMETER_API_KEY:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose upSingle-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses CUSTOMERTHERMOMETER_API_KEY:
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-e AUTH_MODE=env \
-e CUSTOMERTHERMOMETER_API_KEY="$CUSTOMERTHERMOMETER_API_KEY" \
-p 127.0.0.1:8080:8080 \
customer-thermometer-mcpHTTP refuses to start until CONDUIT_S2S_SECRET is a real secret. Local HTTP without a secret is development-only: it binds 127.0.0.1 only and logs a warning.
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" npm run start:http
MCP_ALLOW_INSECURE_DEV=1 npm run start:httpAvailable Tools
10 toolscustomerthermometer_add_recipient_to_listC
Add a recipient to a Customer Thermometer recipient list.
Inputs: listId (required), emailAddress (required), lastName, firstName, +1 more.
customerthermometer_get_blast_resultsB
Get raw survey responses received, optionally filtered by temperature (1=gold,2=green,3=yellow,4=red), blast, or date range.
Inputs: limit, toDate, blastID, fromDate, +1 more.
customerthermometer_get_commentsA
Get free-text comments left with survey responses, optionally filtered by temperature, blast, or date range.
Inputs: limit, toDate, blastID, fromDate, +1 more.
customerthermometer_get_creditsA
Get the number of remaining Thermometer send credits on the account.
Inputs: no named parameters.
customerthermometer_get_happiness_valueB
Get the Happiness Factor (as a percentage) for the account or a filtered set of responses.
Inputs: limit, toDate, blastID, fromDate.
customerthermometer_get_nps_valueB
Get the Net Promoter Score (positive or negative integer) for the account or a filtered set of responses.
Inputs: limit, toDate, blastID, fromDate.
customerthermometer_get_recipient_listsA
List all recipient lists (names and IDs) on the Customer Thermometer account.
Inputs: no named parameters.
customerthermometer_get_thermometersA
List all Customer Thermometer survey templates (Thermometer names and IDs) on the account.
Inputs: no named parameters.
customerthermometer_send_emailC
Send a single Email Thermometer survey to one recipient.
Inputs: listID (required), emailAddress (required), thermometerID (required), blastID, +3 more.
customerthermometer_unsubscribe_recipientB
Add an email address to the account's Customer Thermometer unsubscribe list.
Inputs: emailAddress (required), notify.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool targets a distinct action or resource type, such as listing thermometers, managing recipient lists, sending surveys, or retrieving results. There is slight potential overlap between get_blast_results and get_comments, but their descriptions clarify the raw response vs. free-text comment distinction.
All tools use the consistent customerthermometer_ prefix with clear snake_case naming. The verb+noun pattern is maintained throughout: get_*, add_*, unsubscribe_*, send_*. Naming is predictable and easy for an agent to follow.
Ten tools is a well-scoped size for this survey platform server. Each tool covers a meaningful part of the workflow—listing templates, managing recipients, sending surveys, checking credits, and retrieving results—without unnecessary bloat.
The core survey workflow is well covered: send an email thermometer, manage recipient lists, view credits, and retrieve metrics or raw responses. Minor gaps include no direct way to remove a recipient from a list or fetch detailed single-thermometer configuration, but these are not likely to break common agent tasks.
Maintenance
Related MCP Connectors
Read Thermometers, scores, response rates, survey responses and comments in Customer Thermometer.
NPS, eNPS, CSAT and CES surveys with AI follow-up interviews: create, invite, read results.
AI-native survey & form builder. Manage surveys, responses, analytics, and webhooks.
Create, edit and publish surveys, then read results from your AI chat.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to manage ActiveCampaign CRM, marketing automation, and contact data via 33 tools including contacts, deals, tags, automations, pipelines, custom fields, campaigns, accounts, and webhooks.6521 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceExposes the full Chatwoot API as 129 tools for AI assistants, enabling account, contact, conversation, message, inbox, team, report, help center, automation, and custom attribute management, plus exclusive Kanban and scheduled message features.14 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to manage GorillaDesk customer records, users, and company data through natural language interactions. Supports listing, creating, and updating customers, adding notes, and retrieving company and user information.9MIT

clicksend-mcp-serverofficial
AlicenseBqualityDmaintenanceEnables AI assistants to send SMS and manage messaging workflows through ClickSend, including pricing estimates, contact lists, templates, history, and statistics.6152 npm3MIT