Dieta.ai
Nutrition tracking by Dieta.ai. Read your food log with macros (calories, protein, carbs, fat, fiber
我該用這個嗎
品質與安全性
發現項目(8)
- LOW在 dietaai_goals 中
- LOW在 dietaai_user 中
- LOW在 dietaai_subscription 中
- LOW在 dietaai_diabetes 中
- LOW在 dietaai_integration 中
- LOW在 dietaai_sibionics_data 中
- LOW在 dietaai_sibionics_glucose 中
- LOW在 connect 中
根據工具定義與協定合規性的自動化分析。
上下文成本
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"dieta-mcp": {
"url": "https://api.mcp.ai/p_dieta"
}
}
}遠端端點
https://api.mcp.ai/p_dietastreamable-http它能做什麼
工具清單
工具(19)
🟢dietaai_foods(date, start_date, end_date)
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).
輸入結構描述
{
"type": "object",
"properties": {
"date": {
"type": "string"
},
"start_date": {
"type": "string"
},
"end_date": {
"type": "string"
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢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.
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_user
Perfil básico do usuário: nome, email, userId, fuso horário, idioma e data de criação.
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪dietaai_log(prompt, imageUrl, context)
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).
輸入結構描述
{
"type": "object",
"properties": {
"prompt": {
"type": "string"
},
"imageUrl": {
"type": "string"
},
"context": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_diary(date)
Resumo do diário (journal) de um dia, no formato YYYY-MM-DD.
輸入結構描述
{
"type": "object",
"properties": {
"date": {
"type": "string"
}
},
"required": [
"date"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_diary_scheme
Definições dos itens de diário do usuário (as faixas/tracks que ele acompanha, ex.: glicose).
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_diary_logs(diaryId, start_range_date, end_range_date)
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.
輸入結構描述
{
"type": "object",
"properties": {
"diaryId": {
"type": "string"
},
"start_range_date": {
"type": "string"
},
"end_range_date": {
"type": "string"
}
},
"required": [
"diaryId"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_subscription
Dados da assinatura do usuário no Dieta.ai.
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_diabetes
Configurações/perfil de diabetes do usuário (bloco user_diabetes).
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_integration(provider, path)
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.
輸入結構描述
{
"type": "object",
"properties": {
"provider": {
"type": "string",
"enum": [
"whoop",
"strava",
"oura"
]
},
"path": {
"type": "string"
}
},
"required": [
"provider",
"path"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_libre_data(body)
Dados de glicose do LibreView (Libre). Body opcional, igual ao que o app envia após conectar.
輸入結構描述
{
"type": "object",
"properties": {
"body": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_sibionics_data(body)
Dados de glicose do Sibionics (gráfico). Body opcional, passthrough.
輸入結構描述
{
"type": "object",
"properties": {
"body": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dietaai_sibionics_glucose
Glicose do dispositivo Sibionics. O inviteId vem do perfil do usuário, não é passado pelo cliente.
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢show_version
Show the current MCP platform and adapter versions.
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡report_bug(message, context, conversation)
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
輸入結構描述
{
"type": "object",
"properties": {
"message": {
"type": "string"
},
"context": {
"default": "",
"type": "string"
},
"conversation": {
"default": "[]",
"type": "string"
}
},
"required": [
"message"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢connect
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.
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢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.
輸入結構描述
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡marketplace(action, query, mcp_id, limit, tier_slug, ...)
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.
輸入結構描述
{
"type": "object",
"properties": {
"action": {
"default": "search",
"type": "string",
"enum": [
"search",
"describe",
"install",
"uninstall",
"subscribe",
"cancel",
"resume",
"report_bug",
"request_mcp",
"list_tools",
"invoke",
"search_prompts",
"get_prompt",
"publish_prompt"
]
},
"query": {
"default": "",
"type": "string"
},
"mcp_id": {
"default": "",
"type": "string"
},
"limit": {
"default": 10,
"type": "number"
},
"tier_slug": {
"default": "",
"type": "string"
},
"immediate": {
"default": false,
"type": "boolean"
},
"cancel_reason": {
"type": "string",
"enum": [
"too_expensive",
"missing_features",
"switched_service",
"unused",
"customer_service",
"too_complex",
"low_quality",
"other"
]
},
"cancel_comment": {
"default": "",
"type": "string"
},
"message": {
"default": "",
"type": "string"
},
"report_context": {
"default": "",
"type": "string"
},
"conversation": {
"default": "[]",
"type": "string"
},
"request_name": {
"default": "",
"type": "string"
},
"request_details": {
"default": "",
"type": "string"
},
"tool_id": {
"default": "",
"type": "string"
},
"arguments": {
"default": "{}",
"type": "string"
},
"prompt_slug": {
"default": "",
"type": "string"
},
"prompt_vars": {
"default": "{}",
"type": "string"
},
"prompt_category": {
"default": "",
"type": "string"
},
"prompt_tool": {
"default": "",
"type": "string"
},
"prompt_title": {
"default": "",
"type": "string"
},
"prompt_description": {
"default": "",
"type": "string"
},
"prompt_body": {
"default": "",
"type": "string"
},
"prompt_targets": {
"default": [],
"type": "array",
"items": {
"type": "string",
"enum": [
"claude",
"chatgpt",
"cursor",
"lovable"
]
}
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡authenticate(token)
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.
輸入結構描述
{
"type": "object",
"properties": {
"token": {
"type": "string"
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}社群
證據