anova-oven-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@anova-oven-mcpWhat are the current oven temperatures?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Anova Precision Oven library + MCP server
This project contains two deliberately separate layers:
anova_oven: an async Python library for Anova authentication, device discovery, temperatures, cook control, stages, and APO 2.0 WebRTC camera frames.anova_oven_mcp: a thin MCP 2.x adapter over that library.
The separation keeps the device code reusable in a future Raspberry Pi service or extension without making MCP a core dependency.
Features
Capture one JPEG camera frame or consume frames as an async iterator.
Read the four physical cooking sensors: dry top, dry bottom, wet bulb, and food probe. The active dry control value is returned separately.
Start and stop cooks. Timed stages support 1 second through the oven's maximum of 359,940 seconds (99h 59m); an omitted duration runs until stopped.
Use probe-terminated cooks and sequential, timed, preheat-delayed, or manually advanced stages.
Replace the stage list of an active cook.
Return UTC time-of-day as hours, minutes, and seconds.
Load credentials from macOS Keychain, a private mode-0600 file, or an injected environment secret.
Related MCP server: Mealie MCP Server
Important status and safety notes
Cook commands physically activate an appliance. The MCP tools that start or alter a
cook require acknowledge_physical_action=true, and validate the oven's documented
temperature, timer, probe, heating-element, steam, fan, and rack limits.
The camera path is a private mobile-app protocol, not part of Anova's documented Personal Access Token command surface. It currently requires:
Anova Precision Oven 2.0
an active cook
compatible/current firmware
an eligible Anova subscription
The live-video command or response shape may change with a future Anova app/backend release. Signed playback URLs are kept internal and are never returned by the library or MCP server.
See VALIDATION.md for the completed live sensor, cook, camera, and post-test safety checks.
Installation
Python 3.11 or newer is required. Python 3.12 is recommended.
python3.12 -m venv .venv
source .venv/bin/activate
python -m pip install -e ".[server]"For library use without MCP or video:
python -m pip install -e .Optional extras are camera, mcp, server, and test. A base install keeps the
core library lightweight; the anova-oven-mcp command will direct you to install the
mcp or server extra if its optional runtime is absent.
Credentials
The default credential search order is:
ANOVA_FIREBASE_REFRESH_TOKENthe file named by
ANOVA_FIREBASE_REFRESH_TOKEN_FILEmacOS Keychain generic-password item with:
service
com.codex.anova-camera.firebase-refresh-tokenaccount
anova-oven-mcp
The fixed Keychain account label prevents an older credential under the same service from being selected accidentally. Keychain reads and token rotations use Apple's Security framework directly, so the secret is not placed in process arguments.
Do not put a refresh token in source, MCP configuration, shell history, or logs. For a Pi, a host secret manager or a root-owned mode-0600 credential file is the recommended adapter:
chmod 600 /run/credentials/anova-refresh-token
export ANOVA_FIREBASE_REFRESH_TOKEN_FILE=/run/credentials/anova-refresh-tokenIf more than one oven is paired, set ANOVA_OVEN_ID in the process environment. The
MCP device-list tool deliberately returns only redacted IDs; configure the full ID
outside model-visible context.
MCP server
The local default is stdio, so it opens no listening port:
.venv/bin/anova-oven-mcpA generic desktop MCP configuration looks like:
{
"mcpServers": {
"anova-oven": {
"command": "/absolute/path/to/anova-oven-mcp/.venv/bin/anova-oven-mcp"
}
}
}Available tools:
Tool | Purpose |
| List paired ovens with redacted IDs |
| Read all four physical sensors and dry-control value |
| Return one |
| Start a one-stage timed, probe, or unbounded cook |
| Start a multi-stage cook |
| Replace stages in the active cook |
| Advance to a configured stage UUID |
| Stop cooking and close live video |
| Return UTC hours, minutes, and seconds |
Claude Code and Claude Desktop
The included configurator can register this local stdio server with Claude Code, Claude Desktop, or both. It does not copy Anova credentials into either client.
Preview the changes first:
python scripts/configure_claude.py --dry-runConfigure both clients (Claude Code uses user scope by default):
python scripts/configure_claude.py --target bothUseful alternatives:
# One client only
python scripts/configure_claude.py --target code
python scripts/configure_claude.py --target desktop
# Update an existing same-named Claude Code entry
python scripts/configure_claude.py --target code --replace
# Remove the entry from both clients
python scripts/configure_claude.py --removeClaude Desktop configuration is merged atomically, preserving other servers and
creating a timestamped mode-0600 backup. Quit and reopen Claude Desktop afterward.
For distributing this beyond a local checkout, Anthropic's current preferred format
is an installable MCP Bundle (.mcpb).
For a future Pi service, the same adapter can use Streamable HTTP:
anova-oven-mcp --transport streamable-httpThat binds to 127.0.0.1:8766. A non-loopback bind requires --allow-lan; do not
expose it until an authenticated reverse proxy or MCP authorization layer is in
place.
Library example
import asyncio
from anova_oven import CookPlan, CookingStage, PrecisionOvenClient
async def main() -> None:
async with PrecisionOvenClient() as oven:
temperatures = await oven.get_temperatures()
print(temperatures.as_dict())
plan = CookPlan(
title="Two-stage example",
stages=(
CookingStage(
title="Warm",
target_celsius=60,
duration_seconds=600,
),
CookingStage(
title="Finish",
target_celsius=180,
duration_seconds=300,
),
),
)
# This physically starts the oven:
receipt = await oven.start_cook(plan)
print(receipt.stage_ids)
try:
frame = await oven.capture_frame(timeout=60)
with open("oven-frame.jpg", "wb") as output:
output.write(frame.jpeg_bytes)
finally:
await oven.stop_cook()
asyncio.run(main())For repeated frames, use oven.frames() as an async iterator. MCP intentionally
exposes one-shot images because indefinitely streaming tool calls are poorly portable
between hosts.
Verification
python -m pip install -e ".[server,test]"
ruff check .
mypy src
pytest
python -m pip checkThe read-only account check is:
python scripts/live_read_only.pyThe guarded camera smoke test starts a minimum-temperature three-minute cook, waits for an independent state event confirming that cook, captures one frame, and issues the physical stop before best-effort media cleanup:
python scripts/live_camera_smoke.py --acknowledge-empty-oven-and-start-cookThat test completed successfully against an APO 2.0. The captured validation frame is included as oven-camera-smoke.jpg.
Protocol sources
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables interaction with 3D printer management systems through an MCP server, supporting STL file manipulation, slicing, and control of printers like OctoPrint, Klipper, Duet, and more.103225GPL 2.0
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Mealie for managing recipes, meal plans, shopping lists, foods, units, tags, categories, and more through MCP.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for interacting with Fireboard BBQ temperature monitoring. Enables querying devices, live probe temperatures, Drive fan controller status, and historical cook sessions.MIT
- FlicenseNot gradedqualityBmaintenanceEnables control of external Home Assistant devices via an MCP control layer and frontend system page.
Related MCP Connectors
An authenticated remote MCP server for user-owned devices and one-shot capability invocation.
MCP server wrapping the Tesla Fleet API and TeslaMate API
Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ampdot-io/anova-oven-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server