Documentation — Wetware

What Wetware does

Wetware is a remote MCP server that gives an AI assistant the numeric machinery for nutrition and training: exact TDEE math, a deterministic meal-plan solver, a food diary measured in grams, and a workout log. It handles four groups of work.

Targets & profile

Calorie and macro targets computed from body stats, goal, and activity level — recalculated whenever the profile changes.

Weekly plan & groceries

A 7-day, 3-meal-a-day plan built from a curated recipe catalog, plus one aggregated grocery list covering all 21 meals.

Food diary

What was actually eaten, logged by the gram, checked against the day’s calorie and macro target.

Workout log & food repository

Training sessions and lift sets, tagged and totaled by week — alongside a shared, user-built repository of product macros anyone can search and contribute to.

Connecting

Add Wetware as a connector, then sign in once.

Claude (claude.ai & Desktop)

Open Settings → Connectors (claude.ai: Customize → Connectors).
Search the Connectors Directory for “Wetware” and connect, or choose Add custom connector and paste the address below.
Complete sign-in when prompted.
In a chat, enable Wetware via + → Connectors.

Any MCP-compatible agent

Open its connector or integration settings.
Add a custom remote connector named Wetware using the address below.
Complete sign-in, then enable Wetware for the conversation.

https://mcp.wetware.club/mcp

Sign-in uses OAuth (via Clerk) and appears on the first tool call. Approve it once — your session persists across conversations, and your profile, plans, and diary stay private to your account. See Privacy Policy.

Tool reference

The tools your assistant calls on your behalf. You don’t need to name them — describe what you want in plain language.

Read tools

Tool	Purpose
get_status	Orientation: whether a profile and plan exist, and catalog size
compute_targets	Calorie/macro calculator for a hypothetical profile — nothing saved
get_profile	Saved profile, preferences, and computed daily targets
list_recipes	Browse the curated recipe catalog
get_recipe	Full detail for one recipe: ingredients, instructions, timings
search_foods	Search the shared, user-contributed food repository
get_plan	The active weekly plan, or a specific plan by id
list_plans	Plan history
get_grocery_list	Aggregated shopping list for a plan’s 21 meals
get_diary	A day’s logged food against the day’s target
search_exercises	Browse or filter the exercise catalog by tag
get_training_log	Logged training for a date range, with per-tag totals

Write tools

Tool	Purpose
upsert_profile	Save body stats, goal, and macro preset
set_preferences	Save allergies and liked/disliked foods (full replace)
add_food	Contribute a product’s per-100 g macros to the shared repository
generate_plan	Build and persist a new 7-day, 3-meal plan
swap_meal	Replace one planned meal, rebalancing the day
log_food	Log a repository food into the diary, by grams
log_plan_meal	Log a planned meal as eaten
log_custom_food	Log a one-off food with an estimated macro breakdown
relabel_diary_entry	Fix a diary entry’s meal label (breakfast/lunch/dinner/snack)
remove_diary_entry	Undo a diary entry
add_exercise	Add a new exercise to the catalog
log_exercise	Log a lift set or a timed activity
retag_exercise	Re-tag one of your own exercises (full replace)
remove_workout_entry	Undo a workout log entry

A couple of additional tools power the interactive panels’ internal UI only (for example, fetching swap candidates for the plan board) and aren’t meant to be called directly.

Example prompts

Say what you want in your own words. A few starting points:

Set up targets

“I’m a 30-year-old man, 84 kg, 181 cm, moderately active. I want to get to 78 kg in 12 weeks.”

Computes and saves your daily calorie and macro targets

Plan the week

“Plan next week and turn it into one grocery list.”

Generates the 7×3 plan, then the aggregated list

Log a meal

“For lunch I had 200 g grilled chicken and a small side salad — how much room do I have left today?”

Logs the meal, then reports remaining calories and macros

Swap a meal

“I’m lactose intolerant — swap out tomorrow’s dinner for something dairy-free.”

Replaces the meal with a compliant, rebalanced alternative

Interactive panels

On hosts that support MCP Apps, five entry points open a visual panel instead of a chat reply. Every capability is also reachable through the tools above, so hosts without Apps support lose nothing.

get_started
First-run onboarding: guides a new user through profile, preferences, and their first plan in one panel.
daily_dashboard
The Today panel: calorie-budget ring, one-tap meal logging, and the day’s eaten and trained log.
meal_plan_board
The weekly 7×3 grid: calories vs. target per day, weekly macro split, and one-click meal swaps.
grocery_checklist
A tick-off shopping checklist for the active plan’s aggregated ingredients.
profile_studio
A what-if targets calculator, plus the profile and preferences editor.

Limitations & troubleshooting

Calorie band

Every day in a generated plan lands within ±5% of your calorie target, not exactly on it — a fixed recipe catalog can’t hit every day precisely and still vary the food.

Infeasible plans

If your allergies and dislikes leave too few compliant recipes (heavy combinations, like lactose and gluten together, are the usual cause), plan generation names the blocking constraints instead of returning a partial plan. Relax one and try again.

Allergens

Five allergens — lactose, gluten, nuts, seafood, eggs — are hard-excluded from every plan. Anything else you report is a soft dislike: Wetware can’t guarantee it’s absent, so check ingredients yourself for allergies outside this list.

UTC days

The diary and workout log key on UTC calendar days, not your local time. Logging just after local midnight west of UTC can land on what looks like “yesterday” — say the date explicitly if it matters.

Disconnecting

Remove Wetware from your assistant’s connector settings to revoke access at any time. To also delete your stored data, email [email protected].

Getting help

See Support, or check server status.