Macrofactor MCP vs Garmin Local MCP

setup_check

Check local setup and explain the easiest next action. Use this first when the MCP seems empty, stale, misconfigured, or when you are not sure which tool to call next. Args: show_workflows: Include common question-to-tool workflows.

import_export

Import a MacroFactor .xlsx export file into the database. Supports both Quick Export and All-Time Data formats. If filename is empty, auto-detects the most recent .xlsx in the data directory. Args: filename: Path to .xlsx file, or empty to auto-detect.

clear_data

Clear all imported data so you can reimport fresh exports.

data_status

Check what data is currently loaded — date ranges, row counts, last import.

query

Run a custom SQL query against the MacroFactor database. Available tables: - daily: date, calories, macros, targets, weight, expenditure, steps, micros - food_log: date, time, food details (from Quick Export) - workouts: date, exercise, sets, reps, weight (from Quick Export) - muscle_sets: date, muscle_group, sets - muscle_volume: date, muscle_group, volume_kg - exercise_tracking: date, exercise, metric, value (from All-Time) - body_metrics: date, metric, value - custom_foods: food_name, nutrition info - nutrition_targets: program_date, weekday, targets - food_log_notes: date, name, note - garmin_daily_stats: date, steps, calories, HR, stress, body battery - garmin_activities: activity_id, date, type, duration, distance, HR, power - garmin_sleep: date, sleep phases, score, HRV, SpO2 - garmin_training_status: date, status, VO2max, training load, FTP - garmin_body_fat: date, body_fat_pct - garmin_sync_log: sync history Use `data_status` to see what's loaded. Args: sql: SQL query (read-only SELECT statements only).