MCP server introduction
The MCP server is in beta.
The Nutritionist Pro Model Context Protocol (MCP) server lets AI applications and coding agents read your Nutritionist Pro data through the Model Context Protocol (MCP). Once connected, an assistant such as Claude or Codex can answer questions about your foods, recipes, labels, and nutrients using your own account data, without you copying and pasting anything.
Read-only by design
The MCP server is read-only. It exposes lookup and search operations only. It cannot create, edit, or delete foods, recipes, or labels, and it cannot change any account settings. Connecting an assistant to the server is safe: the worst an assistant can do is read data you already have access to.
If you need to make changes to your data, continue to use the Nutritionist Pro online application directly.
What you can do with it
With the server connected, you can ask an assistant to:
- Search your ingredient and food database and pull up a food's nutrient profile.
- Look up a recipe and review its ingredients and calculated nutrition.
- Find a label and inspect its values.
- Browse the list of nutrients tracked in your account.
- Confirm which account the connection is using.
Available tools
The assistant sees the server's capabilities as a set of tools. The table below lists what is currently exposed.
| Tool | What it returns |
|---|---|
whoami | The account the connection is authenticated as, and how many of today's tool calls have been used. |
list_foods | A paged list of foods and ingredients in your account. |
search_foods | Foods and ingredients matching a search term. |
get_food | The full detail and nutrient profile for a single food. |
list_recipes | A paged list of your recipes. |
get_recipe | The full detail for a single recipe, including ingredients and nutrition. |
list_labels | A paged list of your labels. |
get_label | The full detail for a single label. |
list_nutrients | The nutrients tracked in your account. |
Who it is for
The MCP server is for anyone who works with their Nutritionist Pro data alongside an AI assistant: formulators checking nutrient values, teams drafting label copy, or developers building on top of their data with an agent. It works with desktop AI applications (such as Claude Desktop and Codex) and with command-line agents (such as Claude Code and the Codex CLI).
Get your MCP key
Every connection authenticates with a personal MCP key. Generate one before you configure any app:
- Sign in to Nutritionist Pro online and open the Settings page from the user profile menu in the top-right corner.
- Go to the MCP section and create a new MCP key.
- Copy the key. It begins with
npmcp_. This is the value you paste into your AI app's configuration in place of<MCP_API_KEY>.
An MCP key is tied to the user who created it and grants read access to that account's data. Treat it like a password: do not share it, and do not commit it to a shared repository. If a key is exposed, generate a new one from the Settings page.
When you generate a key, it will only be shown once. Record it in a password manager.
An MCP key does not expire by date. It stops working when your account no longer has an active subscription, and the server then answers with the message "This account has no active subscription." The same key works again once your subscription is active, so there is no need to generate a new one.
Daily limit
Each user can make 500 tool calls per day through the MCP server. The count resets at midnight UTC for everyone, whatever your time zone.
Only tool calls count, such as a search or a recipe lookup. Connecting, listing the available tools, and the other messages an AI app sends on its own do not count. A typical question takes between two and six tool calls, so the limit leaves plenty of room for normal use. It is there to stop an agent that is stuck in a loop.
To see how many calls you have left, ask your assistant to run whoami, which reports the daily limit, the calls used today, and when the count resets. The MCP Server Key card on the Settings page shows the same count, for example "Used today: 42 of 500 tool calls. Resets at midnight UTC."
When the limit is reached, each further tool call returns a message instead of data, which your assistant passes on to you:
Daily MCP limit reached. This Nutritionist Pro user has used all 500 tool calls allowed per day. The limit resets at midnight UTC (2026-10-26T00:00:00Z), in 3 hours 12 minutes. Tell the user when they can try again; do not retry before then.
The connection stays open, and tool calls work again after midnight UTC. If you need a higher limit, contact support@axxya.com.
Next steps
Pick the guide that matches how you work:
- Set up in AI applications — Claude Desktop and the Codex desktop app.
- Set up in CLI tools — Claude Code and the Codex CLI.
The setup guides use the production server URL https://mcp.nutritionistpro.com. Replace <MCP_API_KEY> with the personal MCP key you generated above before connecting.