Server data from the Official MCP Registry
MCP server for Customer Thermometer's customer feedback / NPS survey API.
About
MCP server for Customer Thermometer's customer feedback / NPS survey API.
Security Report
Valid MCP server (2 strong, 1 medium validity signals). 9 known CVEs in dependencies (3 critical, 1 high severity) Imported from the Official MCP Registry. Trust signals: trusted author (61/63 approved).
12 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
Unverified package source
We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.
What You'll Need
Set these up before or after installing:
Environment variable: CUSTOMERTHERMOMETER_API_KEY
Environment variable: MCP_TRANSPORT
Environment variable: AUTH_MODE
Environment variable: LOG_LEVEL
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-wyre-ai-customer-thermometer-mcp": {
"env": {
"AUTH_MODE": "your-auth-mode-here",
"LOG_LEVEL": "your-log-level-here",
"MCP_TRANSPORT": "your-mcp-transport-here",
"CUSTOMERTHERMOMETER_API_KEY": "your-customerthermometer-api-key-here"
},
"args": [
"-y",
"@wyre-ai/customer-thermometer-mcp"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
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
| Env var | Description |
|---|---|
CUSTOMERTHERMOMETER_API_KEY | API key issued by Customer Thermometer. |
MCP_TRANSPORT | stdio (default) or http. |
AUTH_MODE | env (default, reads the var above) or gateway (credential arrives per-request via the X-CustomerThermometer-Api-Key header, injected by the Conduit gateway). |
CONDUIT_S2S_SECRET | When set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request. |
LOG_LEVEL | debug | info (default) | warn | error. |
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 --noEmit
Docker
docker build -t customer-thermometer-mcp .
docker run -p 8080:8080 -e CUSTOMERTHERMOMETER_API_KEY=... customer-thermometer-mcp
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.