Numon MCP server: scoped Numon access for every agent

Start with a date and the account’s local day. A diary entry is recorded information, while the nutritional comments are generated interpretation. Ask the agent to keep those two sources separate rather than presenting an inferred suggestion as something you logged.

For a weekly report, specify the exact date range and make missing days visible. A null score is not a zero, and today’s partial score is not directly comparable with a completed day’s score without that qualification. The range tool expects millisecond timestamps, not seconds.

The fitness profile and macro boundaries can help explain the app’s targets, but they are more personal than a basic diary summary. Use them only when the task needs that context. An agent should not turn an estimated calorie or macro calculation into a diagnosis or a guarantee.

Numon MCP connection options

The catalog connects the Numon OAuth MCP endpoint. Nutrition MCP is another nutrition-related route, but its existence is not evidence that it has identical Numon account access. Inspect the actual selected server rather than treating nutrition tools as interchangeable.

A direct Numon connection can be simpler when that app is all you need. AIPx adds another processor for personal diary data, with agent-specific visibility and reuse alongside other approved connections.

Connect Numon to Claude, Claude Code, Cursor or Codex

Connect Numon with OAuth and inspect the tools exposed for that account. Provider authorization is separate from the AI client’s sign-in to AIPx.

1. Open the AIPx dashboard, choose Numon under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Numon; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Numon

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Numon is the only service you need.

Numon MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Authorize using /mcp, then read a completed Numon diary date. Keep missing entries separate from zeros and generated comments separate from logs. Claude Code MCP setup covers authentication.

Numon MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

Complete Cursor OAuth and enable only the Numon reads relevant to your personal review. A software task normally needs no diary or profile data. See Cursor MCP setup for configuration scope.

Numon MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Numon credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

Custom MCP access in ChatGPT can read the authorized Numon diary through this endpoint. Estimates and current-day scores need their stated qualifications. ChatGPT MCP setup explains supported clients and workspace restrictions.

Scope Numon personal data per agent

A diary summarizer can have get_diary and get_range_report enabled. Keep fitness-profile and preference reads hidden unless they are necessary for the question. A coding agent does not need food or body context just because it can share the same gateway.

General read tools start on Allow. For personal data, the useful recommendation is often narrower than that default. MCP permissions lets you hide tools from unrelated agents without deleting the underlying diary or changing provider data.

Hevy supplies workout logs, WHOOP recovery context and Withings measurements. Keep each source’s definitions and dates visible. Notion can hold a reviewed private summary if you separately authorize that write.

Nutrition estimates, day scores and range limits

Food analysis is estimated, and input quality affects the result. Report source values and missing entries instead of filling gaps with typical meals. Current-day meal-window scoring and completed-day scoring should be identified in comparisons.

Numon account permissions and service limits remain in force. This page does not assert an unverified vendor price or promise writes from the standalone app’s broader tool set. A logged trend can support a personal review, but it is not a medical finding or guaranteed calorie measurement.

Browse all MCP integrations to choose another connection for this agent.

The Numon connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.