Almost Fire
Strength training plans for 26 weeks, plus set, meal and progress logging in Almost Fire.
What it does
Almost Fire is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: debugging. That makes it a candidate for tasks such as fix bugs in a codebase or monitor production incidents.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 21h ago (live check)Hosted endpoint
https://strength.almostfire.com/api/mcpstreamable-http
In Claude Code: claude mcp add --transport http almost-fire https://strength.almostfire.com/api/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"almost-fire": {
"url": "https://strength.almostfire.com/api/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 21h agoONLINE Almost Fire answered an MCP connection on 08 Nov 2026 and introduced itself as almost-fire 1.0.0 (MCP protocol 2025-06-18).
28 tools offered to AI assistants
make_plan· Use this when someone asks for a strength, gym, weightlifting or muscle-building program or workout plan, at a gym or at home. Builds all 26 weeks from Almost Fire's plan engine, the one the app uses: the split for their days, each session'save_plan· Use this when the person wants to keep, save or start a plan make_plan made, or presses Save on its card. Saves the plan to their Almost Fire account, free: the first time it asks them to sign in, which makes their account. Send the answersshow_exercise· Use this when someone asks how to do an exercise, which muscles it works, or what to do instead. Shows it on the body map with its equipment, its cues and swaps that train the same thing. No account needed. Do not use to diagnose pain or toget_today· Use this when the person asks what's on today or how today's session is going, and before logging a set. Reads today's session (or the next one) in their Almost Fire account with every exercise, its target and the sets logged, this week's sget_schedule· Use this when the person asks what's coming up this week or next, or what they did on other days. Lists their sessions between two ISO times (from, to), each with its id, day, time and status. Do not use for today's session; use get_today.get_session· Use this when you need one session in full, by its id from get_today or get_schedule. Reads its exercises (slots) with each target, the exercises each slot allows, and the sets logged. Do not use to list sessions; use get_schedule.log_set· Use this when the person tells you a set they did. Give the session and slot from get_today or get_session, and the load and reps they said. Never invent a number. loadUnit kg or lb as they said it (label for a machine's own numbers); rir oedit_set· Use this when the person corrects a set they already logged. Give its setId from get_today or get_session and only the values they change; null keeps the rest. Comes back with an Undo. Do not use to log a new set; use log_set.delete_set· Use this when the person asks to remove a set they logged by mistake. Give its setId. Comes back with an Undo. Do not use to change a set's numbers; use edit_set.list_alternatives· Use this when the person wants a different exercise in a session (a busy machine, a sore joint, missing kit). Lists the swaps that train the same movement in that slot and week, best first, by sessionId and slot. Nothing changes; swap withswap_exercise· Use this when the person asks to swap the exercise in a session. Give the sessionId and slot, and the exerciseKey they chose, or a same-movement one from list_alternatives when they leave it to you. The new exercise brings its own rules, anupdate_session· Use this when the person starts, finishes or skips a session, or says how it felt. status IN_PROGRESS starts it, DONE finishes it and SKIPPED skips it; feeling is 1 to 5; notes and gym as they say. Null leaves a field as it is. Comes back w
Show 16 more
move_session· Use this when the person asks to move a session to another day or time. Give its sessionId and the new start and end as ISO times. Comes back with an Undo. Do not use to skip a session; use update_session.log_cardio· Use this when the person tells you about cardio they did: a run, a ride, the rower, a walk. Record cardio the person did, with the numbers they give: minutes always; distance, heart rate, level, incline, energy and intervals only when givenrecord_checkin· Use this when the person says how they feel before or after training, or tells you about pain or swelling. Record the person’s reported readiness and symptoms. symptoms.pec is pain anywhere (sharp means sharp pain or pulling) and symptoms.klog_weight· Use this when the person tells you their weight. Give the weight and unit, and when (null is now). Targets follow the smoothed trend, never one reading. Comes back with an Undo. Do not use to set a weight goal.open_camera· Use this when the person wants to log a meal from a photo but hasn't attached one, or the app can't hand you their photo. Opens the Almost Fire camera in the chat: they take or choose a photo there, Stoke reads each food with its grams andread_meal_photo· Use this when the person attaches a photo of food they ate or will eat. Reads it as the Almost Fire camera does: a plate or bowl comes back as each food with its grams, calories, macros and how sure the read is; a packet as its label per 10read_meal_photo_upload· The Almost Fire camera card's photo, read as read_meal_photo reads one. Only the card calls it.search_foods· Use this when the person tells you a food they ate without a photo, before log_foods. Find the person's own foods before anything else, by name or by kind: the words they used ("protein powder", "milk", "my usual bread"), not a brand you gulog_foods· Use this when the person has agreed what they ate and wants it logged. One entry per food: from a photo read (read_meal_photo's logItems, with their corrections), a saved food or recipe by id and grams (from search_foods), or an estimate widelete_food_entry· Use this when the person asks to remove a food they logged by mistake. Give its entry id from get_nutrition. Comes back with an Undo. Do not use for a food they still ate; log the right amount instead.get_nutrition· Use this when the person asks what they've eaten or how their calories and protein are going, and before removing a logged food. Reads a day's food (date null is today): every entry with its id, the totals against the day's targets, their ushow_progress_chart· Use this when the person asks to see their progress on a graph. Draws one of their Progress graphs from their records: lift_max or lift_volume per session for one exercise (key), weekly_volume, body_weight (90 days), cardio_distance, cardioget_progress· Use this when the person asks how they're progressing, in numbers. Reads their Progress page: training volume by week, bests, each lift's estimated max and trend, sessions done, bodyweight and cardio, as the app shows them. Do not use for aget_weekly_review· Use this when the person asks how their week went or what changes next week. Reads the Sunday review of a program week (null is the latest): sessions, volume, new bests, the pace, each change Stoke made to next week with its reason, and whaundo_review_change· Use this when the person doesn't want one of the changes the Sunday review made to next week. Give the change's index from get_weekly_review. Next week goes back to the program's target for that change. Do not use for a change they made theundo· Use this when the person wants to take back a change made here (a logged set, meal, weigh-in or any other) while its Undo is open. Give the undo.id the change came back with. Do not use for a change they made in the Almost Fire app itself.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Tasks it helps with
Share of each task's required capabilities it covers| Fix bugs in a codebase Debugging | 50% |
| Monitor production incidents Debugging | 33% |
Similar tools
Listed for the same task: fix bugs in a codebase- Foam ObservabilityREMOTELOCALQuery application logs, traces, and metrics from your AI coding assistant via Foam's MCP server
- kube-noobREMOTELOCALKubernetes, OpenShift, ROSA HCP, Helm and RHACS audit, debugging and cited docs. No AI inside
- PWA Debug LayerREMOTELOCALDebug PWAs in your real browser via MCP: service-worker, cache, installability & framework state
- OpenFaultREMOTELOCALSelf-hosted, Sentry-compatible error tracker. Agents read and triage issues over MCP
- Kafka MCPREMOTELOCALDebug Kafka from an agent: find messages, measure consumer lag, unblock consumers, compare clusters
- VictauriREMOTELOCALIn-process MCP server for Tauri apps: DOM, IPC with bodies, Rust state, SQLite. Debug builds only
Ready-made AI agents
- $20/mo · Prices & score →
- Free plan · Prices & score →
- Cursor53$20/mo · free plan · Prices & score →
- Amp49$20/mo · free plan · Prices & score →
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Repository | https://github.com/davidgibbon1/almost-fire-plugin | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Version | 1.3.1 | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Hosted endpoint | https://strength.almostfire.com/api/mcp | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Website | https://almostfire.com | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 19h ago |
Change history
- VERSION08 Nov 20261.3.0 → 1.3.1
- NEW08 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Almost Fire still online?
Free alerts · no account▲ 0Do you run Almost Fire? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Almost Fire
How do I connect Almost Fire?
Use the hosted endpoint https://strength.almostfire.com/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Almost Fire offer?
When Electra Index connected on 08 Nov 2026, it listed 28 tools: make_plan, save_plan, show_exercise, get_today, get_schedule, get_session, log_set, edit_set and more. The full list is in "Live check" above.
Is Almost Fire online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 21h ago.
What can I use Almost Fire for?
Based on its description, it is most relevant to: fix bugs in a codebase, monitor production incidents.