Read Thermometers, scores, response rates, survey responses and comments in Customer Thermometer. For customer service teams that measure satisfaction with Customer Thermometer. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"customer-thermometer": {
"url": "https://customer-thermometer.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"customer-thermometer": {
"type": "http",
"url": "https://customer-thermometer.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Read the Happiness Factor, the NPS score and the Temperature Rating for a period.
customerthermometer_get_happiness_value customerthermometer_get_nps_value customerthermometer_get_temperature_rating
Read the survey responses and the comments of a period.
customerthermometer_get_blast_results customerthermometer_get_comments
List the Thermometers. Then read the response rate and count the responses for a date range.
customerthermometer_list_thermometers customerthermometer_get_response_rate customerthermometer_count_responses
List the recipient lists and read the send quota that is left.
customerthermometer_list_recipient_lists customerthermometer_get_send_quota
The login page asks for your Customer Thermometer API key and Key type.
Find it in Customer Thermometer under Automations → API Information (owner or global admin only). Choose Super API key or Sub-API key to match the key you paste. The key is used only to call the API on your behalf and to derive a private account id.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Customer Thermometer API key and Key type. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Customer Thermometer connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
customerthermometer_list_thermometers | read | List Thermometers List the Thermometers (survey templates) in the account with their names and IDs. Returns XML. API: getThermometers. |
customerthermometer_list_recipient_lists | read | List recipient lists List the recipient lists in the account with their names and IDs. Returns XML. API: getRecipientLists. |
customerthermometer_get_send_quota | read | Get send quota Get the number of Thermometer credits left in the account. API: getSendQuota. |
customerthermometer_get_happiness_value | read | Get Happiness Factor Get the Happiness Factor (a percentage) for the account, a Blast or a date range. Uses the newest 100 responses unless limit is set. API: getHappinessValue. |
customerthermometer_get_nps_value | read | Get NPS score Get the Net Promoter Score (an integer, can be negative) for the account, a Blast or a date range. limit only works together with blastID or a date range. API: getNPSValue. |
customerthermometer_get_temperature_rating | read | Get Temperature Rating Get the Temperature Rating (a percentage) for the account, a Blast or a date range. Uses the newest 100 responses unless limit is set. API: getTempRatingValue. |
customerthermometer_get_response_rate | read | Get response rate Get the response rate (a percentage) of Email Thermometer Blasts for the account, a Blast or a date range. Uses the newest 100 responses unless limit is set. API: getResponseRateValue. |
customerthermometer_count_responses | read | Count responses Count the responses for the account, a Blast, a date range or one temperature (1 gold, 2 green, 3 yellow, 4 red). API: getNumResponsesValue. |
customerthermometer_get_blast_results | read | Get survey responses Get the newest survey responses (default 200) with all attached data, as XML. Filter by temperature, Blast or date range. The data holds respondent personal data. API: getBlastResults. |
customerthermometer_get_comments | read | Get response comments Get the newest free-text comments (default 200) left with survey responses, as XML. Filter by temperature, Blast or date range. API: getComments. |
customerthermometer_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
customerthermometer_request_feature | Request a missing feature Tell usefulapi that the user needs something the Customer Thermometer tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
customerthermometer_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Customer Thermometer (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
customerthermometer_cancel_subscription | Cancel the Pro subscription Cancel the caller's Customer Thermometer Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run customerthermometer_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Customer Thermometer server only. Subscribe with customerthermometer_upgrade (it returns a Stripe Checkout link). Cancel any time with customerthermometer_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running customerthermometer_upgrade before then undoes the cancel. Or write to [email protected].
Check customer satisfaction. Read the comments of unhappy customers. Check the response rate. Check recipient lists and send quota. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Customer Thermometer. The server calls the Customer Thermometer API with your own Customer Thermometer access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Customer Thermometer API key and Key type. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Customer Thermometer API key and Key type. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Customer Thermometer API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Customer Thermometer.
All 10 Customer Thermometer tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Customer Thermometer server only. Cancel any time: Pro then runs to the end of the paid period. Run customerthermometer_usage_status to see how many calls you used.
Ask the AI to run customerthermometer_upgrade: it returns a Stripe Checkout link. To cancel, run customerthermometer_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with customerthermometer_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.