Skip to main content
Glama
tempstick-mcp

tempstick-mcp

by obseard223

tempstick-mcp

mcp-name: io.github.obseard223/tempstick-mcp

Temp Stick MCP server by OpenPandora — let your AI assistant check your freezer and temperature sensors.

New to this? Follow the plain-words setup guide — five minutes, short steps, no jargon.

tempstick-mcp is a free, open-source Model Context Protocol (MCP) server for Temp Stick WiFi temperature sensors by Ideal Sciences — a freezer monitor and temperature sensor reader for your AI assistant. It was built for restaurant kitchens (nobody wants to discover a warm walk-in at 6 AM), and it works anywhere a Temp Stick watches something that matters: freezers, fridges, server rooms, greenhouses, homes. Connect it to Claude, Cursor, or any MCP client and just ask:

"What's my freezer at right now?" "Has the walk-in been above 40°F today?" "Is any sensor offline or low on battery?"

The server answers with live data from the official Temp Stick API: temperature (Celsius and Fahrenheit), humidity, battery level, offline status, alert definitions, and recent-reading summaries.

  • Zero dependencies. Pure Python 3 standard library — no pip install of anything. Clone, add your key, go.

  • Read-only. It cannot change a setting, a threshold, or an alert on your account.

  • Private by design. Your API key stays on your machine in an environment variable. The server talks only to tempstickapi.com.

Tools

Tool

What it returns

list_sensors

Every sensor your key can see, with its latest temperature, humidity, battery and offline status.

get_sensor

The latest reading for one sensor (by sensor_id).

get_freezer_status

One-call check for a sensor: latest reading + recent history summary + alert definitions together. Named for the classic freezer use case; works for any sensor.

get_readings_history

A summary of a sensor's recent readings: count, min / max / average temperature, first and last reading times.

get_alerts

The account's alert definitions and whether they are triggered.

A command-line twin is included for terminal checks and cron jobs: tempstick.py list-sensors, latest --sensor <ID>, history --sensor <ID>, alerts, freezer --sensor <ID>.

Related MCP server: Tessie MCP Server

Get your API key

  1. Sign in at mytempstick.com.

  2. Open the Account Page.

  3. Select the Developers tab.

  4. Click Show Key to reveal your API key.

(Per Temp Stick's official developer documentation.)

Install

git clone https://github.com/obseard223/tempstick-mcp

Claude Desktop

Add to your claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "tempstick": {
      "command": "python3",
      "args": ["/path/to/tempstick-mcp/server.py"],
      "env": { "TEMPSTICK_API_KEY": "paste-your-key-here" }
    }
  }
}

Restart Claude Desktop, then ask: "List my Temp Stick sensors."

Claude Code

claude mcp add tempstick \
  --env TEMPSTICK_API_KEY=paste-your-key-here \
  -- python3 /path/to/tempstick-mcp/server.py

Cursor

Add to .cursor/mcp.json in your project (or the global MCP config):

{
  "mcpServers": {
    "tempstick": {
      "command": "python3",
      "args": ["/path/to/tempstick-mcp/server.py"],
      "env": { "TEMPSTICK_API_KEY": "paste-your-key-here" }
    }
  }
}

On Windows, use python instead of python3 (and a Windows-style path).

Test it offline

No key, no network:

python3 selftest.py            # full end-to-end test against a stub API
python3 tempstick.py selftest  # parsing/unit checks only

Both should end in PASS.

Notes on the API

A few behaviors of the Temp Stick API this server handles for you:

  • Errors come back as HTTP 200 with a JSON envelope (type: "error"), so the server checks the envelope and surfaces the real message — e.g. Invalid X-API-KEY.

  • Temperatures arrive in Celsius; every reading is also reported in Fahrenheit.

  • The API host rejects non-browser user agents, so the server sends a browser user agent.

Status

Community project, built against the official Temp Stick API. It is not affiliated with or endorsed by Ideal Sciences or Temp Stick. The parsing and protocol layers are covered by offline fixture tests (see selftest.py); readings and alerts shapes beyond the documented fields are parsed defensively.

Built by OpenPandora

Built by OpenPandora — AI tools for independent restaurants. This is the same sensor watch that keeps an eye on our pilot kitchen's walk-in freezer, released free because every operator with a Temp Stick should be able to ask their AI about it.

License

MIT — see LICENSE.

Available Tools

5 tools
get_alertsA

List the alert definitions and state for the account (thresholds, delivery channels, whether triggered).

Inputs: no named parameters.

get_freezer_statusA

One-call status check for a sensor (named for the classic freezer use case): latest reading, recent history summary and the account's alert definitions together, so the assistant can answer 'is it OK?' in a single call.

Inputs: sensor_id (required).

get_readings_historyA

Summarize a sensor's recent readings: count, min, max and average temperature (Fahrenheit), and the first and last reading times.

Inputs: sensor_id (required).

get_sensorA

Get the latest reading for one sensor: temperature (Celsius and Fahrenheit), humidity, last check-in, battery level and offline status.

Inputs: sensor_id (required).

list_sensorsA

List the Temp Stick sensors visible to your API key, with each sensor's latest temperature, humidity, battery level and offline status.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    Core tools (list_sensors, get_sensor, get_readings_history, get_alerts) target distinct resources, but get_freezer_status overlaps with three of them by bundling latest reading, history summary, and alerts. Its composite 'is it OK?' purpose is clearly described, so an agent can usually distinguish when to use it.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern: list_sensors, get_sensor, get_readings_history, get_alerts, and get_freezer_status. The singular/plural distinction in list_sensors and get_sensor is predictable and readable.

    Tool Count5/5

    Five tools is well-scoped for a sensor monitoring integration. Each tool has a plausible role, and the set avoids both thinness and bloat.

    Completeness4/5

    The surface covers the main read-only workflows: listing sensors, fetching latest readings, summarizing history, checking alerts, and a one-call status helper. Minor gaps exist around alert state changes or sensor configuration, but these may be outside the API's intended scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Mender IoT platform for device management, deployment monitoring, and fleet analysis through natural language commands. Provides read-only access to device status, deployment logs, releases, and system monitoring capabilities.
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read sensor data from IoT devices and dispatch data collection tasks through a unified interface supporting multiple protocols.
      17
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to AlertOps incident alerting and on-call data, including alerts, users, groups, integrations, and schedules, for AI assistants.
      11
      Apache 2.0