Customer Thermometer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | `env` (default, reads the var above) or `gateway` (credential arrives per-request via the `X-CustomerThermometer-Api-Key` header, injected by the Conduit gateway). | env |
| LOG_LEVEL | No | `debug` | `info` (default) | `warn` | `error`. | info |
| MCP_TRANSPORT | No | `stdio` (default) or `http`. | stdio |
| CONDUIT_S2S_SECRET | No | When set, the HTTP transport requires a valid `X-Gateway-S2S` header (Conduit sidecar auth) on every `/mcp` request. | |
| CUSTOMERTHERMOMETER_API_KEY | Yes | API key issued by Customer Thermometer. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| customerthermometer_get_thermometersA | List all Customer Thermometer survey templates (Thermometer names and IDs) on the account. |
| customerthermometer_get_recipient_listsA | List all recipient lists (names and IDs) on the Customer Thermometer account. |
| customerthermometer_add_recipient_to_listC | Add a recipient to a Customer Thermometer recipient list. |
| customerthermometer_unsubscribe_recipientB | Add an email address to the account's Customer Thermometer unsubscribe list. |
| customerthermometer_send_emailC | Send a single Email Thermometer survey to one recipient. |
| customerthermometer_get_creditsA | Get the number of remaining Thermometer send credits on the account. |
| customerthermometer_get_nps_valueB | Get the Net Promoter Score (positive or negative integer) for the account or a filtered set of responses. |
| customerthermometer_get_happiness_valueB | Get the Happiness Factor (as a percentage) for the account or a filtered set of responses. |
| 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. |
| customerthermometer_get_commentsA | Get free-text comments left with survey responses, optionally filtered by temperature, blast, or date range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.