Dieta.ai vs Mirobody

A side-by-side look at the Dieta.ai and Mirobody MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Dieta.ai logoDieta.aiBiology & Bioinformatics · Remote HTTP/SSENutrition tracking by Dieta.ai. Read your food log with macros (calories, protein, carbs, fat, fiber56GoodAuth: not declaredMirobody logoMirobodyBiology & BioinformaticsTurn scattered health data into answers you can trace. Self-hosted AI health data engine for lab reports, wearables and genetics, with a built-in MCP server. Run it with Docker and one LLM key, or keep every model local on llama.cpp.51GoodAuth: not declared

Verdict: choose Dieta.ai for biology & bioinformatics work over a hosted endpoint; choose Mirobody for biology & bioinformatics. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Dieta.ai logoChoose Dieta.ai when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like dietaai_foods, dietaai_goals, dietaai_user.
Explore Dieta.ai

Mirobody logoChoose Mirobody when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
Explore Mirobody

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDieta.ai logoDieta.aiMirobody logoMirobody
CategoryBiology & BioinformaticsBiology & Bioinformatics
Quality signal56/100 · Good51/100 · Good
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthNot declaredNot declared
PricingNot declaredBYOK (pay the provider)
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars01,389
Directory activity 0 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools19Not listed

Tools & capabilities

Dieta.ai tools 19

  • dietaai_foodsConsulta o log de alimentos do usuário com os macros. Use date para um único dia (YYYY-MM-DD) OU start_date/end_date para um intervalo (máx 31 dias). Retorna os itens por refeição e os totais do dia (kcal, proteína, carbo, gordura, fibra, sódio, água).
  • dietaai_goalsMetas nutricionais do usuário (calorias, proteína, carbo, gordura, água, fibra e metas customizadas). Compare com os totais de dietaai_foods para avaliar a aderência.
  • dietaai_userPerfil básico do usuário: nome, email, userId, fuso horário, idioma e data de criação.
  • dietaai_logRegistra uma refeição enviando texto e/ou a URL de uma foto pro mesmo pipeline de IA do chat do app (reconhece alimentos e calcula macros). Pelo menos um de prompt ou imageUrl é obrigatório. É fire-and-forget (retorna aceito, o processamento é assíncrono).
  • dietaai_diaryResumo do diário (journal) de um dia, no formato YYYY-MM-DD.
  • dietaai_diary_schemeDefinições dos itens de diário do usuário (as faixas/tracks que ele acompanha, ex.: glicose).
  • dietaai_diary_logsLinhas históricas de um track do diário (ex.: série de glicose). diaryId é obrigatório; start_range_date e end_range_date filtram o intervalo quando ambos são informados.
  • dietaai_subscriptionDados da assinatura do usuário no Dieta.ai.
  • dietaai_diabetesConfigurações/perfil de diabetes do usuário (bloco user_diabetes).
  • dietaai_integrationPonte HTTP para a API oficial de um wearable ligado à conta (Whoop, Strava ou Oura). O path segue a doc do fornecedor, ex.: Whoop "v1/cycle", Strava "api/v3/athlete", Oura "v2/usercollection/daily_activity". O vínculo OAuth é feito uma vez no app Dieta.ai.
  • dietaai_libre_dataDados de glicose do LibreView (Libre). Body opcional, igual ao que o app envia após conectar.
  • dietaai_sibionics_dataDados de glicose do Sibionics (gráfico). Body opcional, passthrough.
  • +7 more on the listing page

Mirobody tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Dieta.ai

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dieta-ai": {
      "url": "https://api.mcp.ai/p_dieta"
    }
  }
}

Mirobody

No confirmed install command for Mirobody yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Dieta.ai is categorized under Biology & Bioinformatics and uses a remote HTTP/SSE transport. Mirobody belongs to Biology & Bioinformatics and uses an install path we have not confirmed yet. Pick Dieta.ai for biology & bioinformatics work and Mirobody for biology & bioinformatics.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Mirobody has no confirmed install command yet — follow its own setup instructions.

Dieta.ai has no declared pricing — check the project's own site. Mirobody is bring-your-own-key: usage is billed by the API provider you supply a key for. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add dieta-ai and mirobody as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dieta.ai has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Mirobody has 51/100 (Good) with 3 views, 0 installs and 1,389 GitHub stars.