Dieta.ai

io.github.mcp-dirPublished by GitHub account mcp-dirv0.1.0Updated Oct 26, 2026

Nutrition tracking by Dieta.ai. Read your food log with macros (calories, protein, carbs, fat, fiber

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Dieta.ai nutrition tracking: lets an assistant read your food log and macros, check goals, log meals, and pull glucose and wearable data.

What you can do
  • Read food log entries by meal with daily macro totals, and compare them against nutritional goals
  • Log a meal from text and/or a photo URL through the app's AI food-recognition pipeline
  • Read the user profile, subscription data, diabetes settings and daily diary summaries
  • Fetch diary track definitions and historical track rows such as glucose series
  • Pull glucose data from Libre and Sibionics devices, and query a linked Whoop, Strava or Oura account through a passthrough HTTP bridge
  • Inspect toolkit and connection status, search the mcp.ai marketplace, report bugs and authenticate
When to use it
Useful when you want an assistant to review your diet against your goals, record meals hands-free, or bring glucose and wearable data into a conversation about nutrition and health tracking.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A Dieta.ai account with data already in the app, plus OAuth links made once in the app for wearables. The authenticate tool describes logging in via browser and passing an access token as an Authorization Bearer header.
Before you install
The server handles health data: food logs, glucose readings, diabetes profile, subscription details and wearable data. Logging a meal sends text and photo URLs into the app's AI pipeline and returns before processing finishes. The integration tool forwards arbitrary paths to third-party wearable APIs. An access token is required; keep it out of shared configs.

Installation

In SourceWeft

  1. Open Dieta.ai in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mcp-dir%2Fdieta-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dieta-ai": {
      "type": "http",
      "url": "https://api.mcp.ai/p_dieta"
    }
  }
}

README

This repository has no README.

Tools

19

dietaai_foods

Consulta 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).

Parametersdateend_datestart_date

dietaai_goals

Metas 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.

Takes no parameters.

dietaai_user

Perfil básico do usuário: nome, email, userId, fuso horário, idioma e data de criação.

Takes no parameters.

dietaai_log

Registra 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).

ParameterspromptcontextimageUrl

dietaai_diary

Resumo do diário (journal) de um dia, no formato YYYY-MM-DD.

Parametersdaterequired

dietaai_diary_scheme

Definições dos itens de diário do usuário (as faixas/tracks que ele acompanha, ex.: glicose).

Takes no parameters.

dietaai_diary_logs

Linhas 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.

ParametersdiaryIdrequiredend_range_datestart_range_date

dietaai_subscription

Dados da assinatura do usuário no Dieta.ai.

Takes no parameters.

dietaai_diabetes

Configurações/perfil de diabetes do usuário (bloco user_diabetes).

Takes no parameters.

dietaai_integration

Ponte 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.

Parameterspathrequiredproviderrequired

dietaai_libre_data

Dados de glicose do LibreView (Libre). Body opcional, igual ao que o app envia após conectar.

Parametersbody

dietaai_sibionics_data

Dados de glicose do Sibionics (gráfico). Body opcional, passthrough.

Parametersbody

dietaai_sibionics_glucose

Glicose do dispositivo Sibionics. O inviteId vem do perfil do usuário, não é passado pelo cliente.

Takes no parameters.

show_version

Show Version

Show the current MCP platform and adapter versions.

Takes no parameters.

report_bug

Report Bug

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Parameterscontextmessagerequiredconversation

connect

Connection Status

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Takes no parameters.

toolkit_info

Toolkit Info

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Takes no parameters.

marketplace

Marketplace

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

Parameterslimitqueryactionmcp_idmessagetool_idargumentsimmediatetier_slugprompt_bodyprompt_slugprompt_tool+11 more

authenticate

Authenticate

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

Parameterstoken

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.