Let your AI tools read the machine.

What it is

The Model Context Protocol (MCP) is an open standard that lets AI assistants call tools provided by other software. Tempered's Developer Hub implements an MCP server over Streamable HTTP at http://127.0.0.1:47896/mcp, so a local assistant can read your PC's real state instead of inferring it.

The practical difference: ask an AI assistant “what's eating my RAM?” without this and it will spawn its own shell commands and interpret raw output. With Tempered connected, it gets the same measured, grouped, conservatively classified process list the app itself shows — including the “unknown means unknown” discipline, so nothing gets confidently mislabelled.

The eleven tools

Every tool observes. None of them intervene.

• get_app_info — Tempered version, plan, elevation, and mode flags.
• get_live_metrics — the latest live snapshot: CPU/RAM/GPU load and temperatures, network throughput, disks, uptime.
• list_processes — every running process group with RAM, CPU, and its conservative classification (essential / safe to suspend / unknown).
• list_services — Windows services with state and start mode.
• list_startup_entries — everything set to run at boot: registry Run keys, the Startup folder, and Task Scheduler.
• list_installed_apps — installed programs from the registry, with publisher, version, and size.
• get_specs — full hardware and OS specs, read from Windows on demand.
• list_tweaks — the safe-tweak catalog with each tweak's current measured state.
• scan_junk — measures junk categories (temp files, caches, Recycle Bin). Sizes only; it deletes nothing.
• get_change_ledger — the Undo Center ledger: every change Tempered has made, with previous values.
• get_process_watch_log — Process Watch status and its log of short-lived process sightings.

Setup

The Developer Hub is a Torque feature and is off by default. In Tempered, open Develop → Developer Hub and turn it on. The screen then shows your endpoint and access token, along with ready-made connection snippets.

Claude Code — copy the one-line command from that screen and run it. It has the form:

claude mcp add --transport http tempered http://127.0.0.1:47896/mcp --header "Authorization: Bearer YOUR_TOKEN"

Claude Desktop — copy the JSON block and paste it into your MCP server config. It declares an http server pointed at the same endpoint with the same Authorization header.

Any other MCP client works too: it is a standard Streamable HTTP MCP server, so anything that speaks the protocol and can send a bearer token can connect. Tempered must be running on the same PC, with the hub toggled on.

Security model

Handing an AI tool a window into your machine deserves real boundaries, so the hub is layered rather than trusting a single switch:

• Read-only, by construction. No action tools exist in the server. There is nothing to authorize, because there is nothing to change — modifying anything still requires a click in the app.
• Off by default. Nothing listens until you turn the hub on.
• Local only. The server binds to 127.0.0.1. It is not reachable from your network, let alone the internet.
• Token required. Every request needs a bearer token that is generated locally and shown only inside the app. Regenerate it at any time to cut off anything using the old one.
• Never a browser. Any request carrying an Origin header is refused, so a web page cannot probe the endpoint even from your own machine.
• Every call on record. The Developer Hub screen lists recent calls with timestamps — the same ledger discipline the rest of the app follows.

Nothing is sent to Tempered's servers or anywhere else. The data never leaves your PC; the hub simply answers local questions from local software.

Requirements

Windows 10 or 11 (64-bit), Tempered 0.2.4 or newer, and a Torque or Torque Max plan. The MCP client must run on the same PC. See the FAQ for plan details, or the privacy policy for exactly what does and does not leave your machine.