Enshape

● Active

com.enshapeapp/enshape

Read your private Enshape diary and log meals through scoped account authorization.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "enshape": {
      "url": "https://enshapeapp.com/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http enshape https://enshapeapp.com/mcp
VS Code
code --add-mcp '{"name":"enshape","type":"http","url":"https://enshapeapp.com/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Food, Home & Lifestyle
Version
1.0.1
Registry
active
Published
11/19/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: Enshape is maintained, hosted endpoint answering without a key.

Maintained
Active
Last commit 3 days ago (Nov 19, 2026), 0 open issues.
Official registry
Active
Published as com.enshapeapp/enshape in the official MCP registry, version 1.0.1.
Source
No licence found
Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to enshapeapp.com: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 10:07 UTCStatus history & uptime →
● Working121 msprotocol 2025-06-18v1.1.0toolsprompts

The endpoint answered the MCP handshake as "Enshape" and listed 14 tools. Answering since Nov 19, 2026.

Context cost ≈ 10k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 14 tools.

Tools (14)

  • get_daily_summary1 param

    Returns saved daily targets, quantity-weighted logged calories and macros, signed remaining and explicit overages for a strict user-local YYYY-MM-DD date. Missing or invalid nutrition is incomplete, never zero-filled; unknown totals and remaining are null. One shared diary call. No recommendations or writes.

    Show parameters
    • datestringrequired
  • get_nutrition_targets

    Returns only saved daily calories, protein, carbs, fat and fiber targets, with missing targets explicit. No recommendations or guessed goals. Requires meals:read and consumes one shared diary call.

  • get_meals3 params

    Returns a bounded page of the connected account’s private meals for a local calendar date, including persisted IDs and saved nutrition. When hasMore is true, nextAfterId is the afterId for the next page. Oversized entries are marked for checking in Enshape. Each page consumes one diary call.

    Show parameters
    • datestringrequired
    • afterIdinteger
    • limitinteger
  • recent_foods

    Returns up to 50 recent private diary entries for the connected account, including their dates and saved nutrition.

  • get_nearby_meal_suggestions9 params

    Suggests meals at restaurants near coordinates supplied by the user, from meal combinations saved in Enshape. Returns at most 10 suggestions with restaurant address and distance, saved nutrition, serving info, component items and a nutritionSource for a later confirmed diary entry. Unpersonalized unless targets are passed, or useSavedTargets is true (saved daily targets are whole-day totals, not a per-meal budget; add date to subtract that day’s diary). Menu freshness and availability are unknown, so the user must check the official current menu. The location is used only for this search and is not stored or shared. Each call consumes one diary call from the shared allowance. Never writes to the diary.

    Show parameters
    • latitudenumberrequiredLatitude of the place to search around, in degrees, given by the user. Never guess it from the device, IP address or a place name.
    • longitudenumberrequiredLongitude of the place to search around, in degrees, given by the user.
    • radiusMilesnumberSearch radius in miles. Defaults to 10, maximum 25.
    • limitintegerNumber of meal suggestions to return. Defaults to 5, maximum 10.
    • excludedRestaurantsarrayRestaurant chains to leave out, by name. Case and punctuation are ignored; partial names do not match.
    • targetsobjectNutrition goals for this one meal, in calories and grams. All five values are required. Omit for unpersonalized suggestions.
    • useSavedTargetsbooleanPersonalize with the connected account’s saved DAILY targets. Only true opts in. These are whole-day totals, not a per-meal budget, unless date is also given or
    • datestringWith useSavedTargets, the user’s local calendar date (YYYY-MM-DD). Scores against saved daily targets minus what the diary already holds for that date.
    • savedTargetModestringWith useSavedTargets: whole_day (default) scores against the daily totals (minus the diary when date is given); meal_share scores against one meal’s share as th
  • find_foods6 params

    Searches Enshape by name, without a location: verified restaurant menu items and reviewed restaurant meals (optionally within one restaurant chain), plus the user’s own saved foods and recipes. Returns at most 10 items per page with a ref, per-serving nutrition, provenance and, with meal targets, Enshape’s fit score and reasons; follow nextCursor for more. A menu item is one item, not a complete meal. Restaurant data may be out of date: tell the user to check the official current menu. Log a result only after the user confirms it, with log_food_reference. Each call consumes one diary call. Never writes.

    Show parameters
    • querystringrequiredFood or dish words, optionally with the restaurant, e.g. "chicken burrito bowl" or "Chipotle chicken bowl". Filler words are ignored; every remaining word must
    • restaurantstringRestaurant chain to search within, by name. Case and punctuation are ignored ("chick fil a" matches Chick-fil-A). With a restaurant, query words narrow its menu
    • kindsarrayWhat to search: restaurant (verified menu items and reviewed meals), mine (foods the user saved in Enshape), recipe (the user’s recipes, per serving). Default:
    • targetsobjectGoals for this one meal (calories and grams; all five required). Ranks results by Enshape’s fit score and explains the fit. Omit to rank by match.
    • limitintegerResults per page, at most 10.
    • cursorstringnextCursor from the previous page of this same search.
  • get_usual_meals3 params

    Returns up to 10 distinct foods the user logs most, from their newest 300 diary entries on or before a local date, ranked by meal slot (when given), how often and how recently, with the latest portion, saved per-serving nutrition and a diary ref for log_food_reference. Nothing is logged: confirm the food, portion, slot and date first. Each call consumes one diary call.

    Show parameters
    • datestringrequiredUser’s local calendar date (YYYY-MM-DD). Only entries on or before it are read.
    • mealSlotstringRank foods usually logged in this slot first.
    • limitinteger
  • get_nutrition_trends2 params

    Returns per-day logged totals for up to 31 user-local dates in one consistent read, with averages over complete logged days (count stated), target-hit days when daily targets are set, and the logged-day streak ending at endDate. Unknown values stay null and never become zero; unlogged days are not zero days. Factual diary totals only, no advice. One diary call for the whole range.

    Show parameters
    • startDatestringrequiredFirst user-local calendar date (YYYY-MM-DD), inclusive.
    • endDatestringrequiredLast user-local calendar date (YYYY-MM-DD), inclusive; at most 31 days after startDate counting both ends.
  • update_nutrition_targets6 params

    Changes only explicitly confirmed daily calories, protein, carbs, fat or fiber targets for the connected account. Omitted fields are preserved. Requires separate targets:write consent, at least one whole-number target, and confirmed:true. Returns the exact saved targets read back under the account lock. No automatic recommendations, profile, micronutrient or diary changes. Each valid attempt uses one shared diary call. After an uncertain outcome read targets before repeating an explicitly confirmed patch.

    Show parameters
    • caloriesinteger
    • proteininteger
    • carbsinteger
    • fatinteger
    • fiberinteger
    • confirmedbooleanrequiredUser explicitly confirmed these exact target values. Unspecified targets are preserved.
  • log_meal14 params

    Creates one private diary entry for the connected account after the user confirms the portion, per-serving nutrition, local date and meal slot. Requires all five nutrition values and their source. Approved estimates are labeled. After an uncertain save, check the diary before retrying with the same requestId. Identical retries return the existing entry. Changed payloads are rejected.

    Show parameters
    • datestringrequiredUser’s local calendar date in YYYY-MM-DD format.
    • requestIdstringrequiredIdempotency key for one intended meal. Identical retries return the original meal; different payloads using this key are rejected.
    • namestringrequired
    • caloriesnumberrequired
    • proteinnumberrequired
    • carbsnumberrequired
    • fatnumberrequired
    • fibernumberrequired
    • quantitynumber
    • servingSizestring
    • mealSlotstringrequired
    • nutritionSourcestringrequiredSource of per-serving nutrition: user-provided, food label, official menu, or an explicitly user-approved estimate.
    • estimatedbooleanTrue if any nutrition value is an estimate approved by the user.
    • confirmedbooleanrequiredUser explicitly requested logging these values, portions and date, and accepted any estimates.
  • log_food_reference6 params

    Creates one confirmed private diary entry from a ref returned by find_foods (verified menu item, reviewed restaurant meal or the user’s own food), get_nearby_meal_suggestions (combo) or get_usual_meals, get_meals and recent_foods (diary entry); own foods and diary entries need meals:read too. Enshape resolves and saves the per-serving nutrition, including micronutrients when known, and, when the grant includes meals:read, returns the saved values and totals to read back. Requires quantity, local date, meal slot and confirmed:true after the user confirms. Identical retries with the same requestId return the existing entry; a different request under it is rejected. Does not change the catalog.

    Show parameters
    • datestringrequiredUser’s local calendar date in YYYY-MM-DD format.
    • requestIdstringrequiredIdempotency key for one intended entry. A retry with the same reference, quantity, slot and date returns the original entry; anything else under this key is rej
    • mealSlotstringrequired
    • quantitynumberServings of the referenced food (per-serving values are multiplied by it).
    • refobjectrequired
    • confirmedbooleanrequiredUser explicitly confirmed this food, portion, meal slot and date.
  • delete_meal2 params

    Permanently deletes one private diary entry belonging to the connected account after the user explicitly confirms that exact entry. Use its saved diary ID from Enshape and verify ambiguous or stale entries before deleting. If the outcome is uncertain, check the diary before retrying with the same ID. A deleted:false result means the entry is absent and does not identify who removed it. Each valid attempt, including retries and missing entries, consumes one shared diary call. Only the private diary is affected.

    Show parameters
    • mealIdintegerrequiredPersisted private diary entry ID, not a catalog ID.
    • confirmedbooleanrequiredUser explicitly confirmed deletion of this exact diary entry.
  • request_restaurant5 params

    Stores a restaurant request in a private moderation inbox after explicit user confirmation. Requires restaurant name, a short message, and a stable requestId; optionally a coarse town or city. Never provide precise location, private contact details or diary content. Never creates restaurants or imports menu data, and makes no promise of addition or a reply. Uses one shared assistant allowance attempt; submissions also share a stricter 3 per rolling 24 hours limit per account across web, mobile and assistants. Reuse requestId after uncertain outcomes.

    Show parameters
    • requestIdstringrequired
    • messagestringrequired
    • restaurantNamestringrequired
    • restaurantCitystring
    • confirmedbooleanrequired
  • get_account_status

    Returns server-verified Premium status, diary tool usage, remaining Free allowance, UTC reset time and request caps for the connected account. An unavailable entitlement check reports unknown, never Premium. This lookup does not consume the diary allowance and remains subject to request rate limits. Does not sell or upgrade subscriptions.

Checked by Serverdex with a plain initialize + tools/list call to enshapeapp.com/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 19, 2026
Stars
0
Forks
0
Last push
Nov 19, 2026
License
—

From the README

Enshape assistant connections Connection metadata and setup instructions for Enshape's hosted, proprietary MCP service. This repository contains no application or server source, credentials, or user data. • Website and account setup: https://enshapeapp.com/integrations • Remote Streamable HTTP endpoint: https://enshapeapp.com/mcp • Claude community connector: https://claude.ai/directory/enshape • Official MCP Registry: https://registry.modelcontextprotocol.io/v0.1/servers/com.enshapeapp%2Fenshape/versions/latest • Support: https://enshapeapp.com/feedback • Privacy: https://enshapeapp.com/privacy-policy • Terms: https://enshapeapp.com/terms-and-conditions Connect your own account Each person connects their own Enshape account from their own assistant. This MCP integration provides diary tools; it does not run model inference or route customer requests through the developer's personal agent account. Your assistant provider's plan and usage rules apply. For Codex CLI: For Claude Code: For Claude web/mobile, select Enshape in the connector directory, or add the server URL in the account's custom connector settings, then complete Enshape OAuth. Claude Code and web/mobile connections have separate authentication. Eligible Gemini accounts can add that URL through Connected Apps → Custom apps. Google controls eligibility and available conversation modes.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://enshapeapp.com/mcp

The most-starred Food, Home & Lifestyle servers in the index, with their live-check result.

ServerStarsLast pushLive check
ShipSwift3,278Nov 2026Working
Anime Garden1,408Nov 2026Working
StyleKit876Nov 2026Working
HEARTH364Nov 2026Local / not checked
OpenFate Bazi MCP162Sep 2026Local / not checked

Enshape: questions people ask

Is Enshape a remote or a local MCP server?
According to its entry in the official MCP registry, Enshape ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Enshape need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Enshape safe to use?
Mostly fine: Enshape is maintained, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Enshape still maintained?
Active: the repository's last commit 3 days ago. Last push Nov 19, 2026, 0 GitHub stars. Read from GitHub on Nov 19, 2026.
What tools does Enshape expose?
14 tools as listed by the server itself during the live check, including get_daily_summary, get_nutrition_targets, get_meals, recent_foods, get_nearby_meal_suggestions. The full list with parameters is in the Live check section above.
How do I add Enshape to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Food, Home & Lifestyle →

Add the badge to your site

Show visitors that Enshape is listed here — it’s also the link we check for a free listing.

Enshape — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/com-enshapeapp-enshape?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Enshape — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Enshape — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/com-enshapeapp-enshape?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/com-enshapeapp-enshape) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/com-enshapeapp-enshape) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/com-enshapeapp-enshape)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/com-enshapeapp-enshape"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/com-enshapeapp-enshape"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/com-enshapeapp-enshape"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).