Resources · Claude connector

Claude Alma connectorWhat Claude can do in your Alma account.

The Claude Alma connector exposes 5 tools. All 5 read your nutrition data, 0 write anything, 0 are undocumented. Here: what Claude can look at in your Alma log, what Alma asks of you first, and what the official sources leave out.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can see your Alma log

Alma is an AI nutrition coach that tracks what you eat, follows more than 25 micronutrients per meal and scores the quality of your diet. Once it is connected, you no longer paste screenshots into a chat: Claude reads your own meals, score, goals, weight history and profile, and answers questions about your actual diet rather than a generic one.

A straight answer about last week. You wonder why the week felt off: get_meal_data gives Claude your logged meals, so the reply rests on what you really ate, not on what you remember.

A trend instead of a single number. With get_alma_score_data, Claude can talk about how your Alma Score has moved, which is more useful than a one-day snapshot when you are changing habits.

Advice measured against your own targets. get_goals and get_weight_history let Claude set its suggestions next to what you aimed for and where your weight has actually gone.

What Claude will not do with this connector: by default the directory sheet only exposes reading, so none of these tools logs a meal, edits a goal or changes your profile. Alma's authorization does mention a write scope, but no listed tool uses it. And the connector never acts by itself: no reminder fires when you skip a meal. Background jobs of that kind are an automation tool's trade, a different one; the Integrations hub covers that side.

Vocabulary

Five words before you connect

The terms you will meet when you link Alma to Claude.

Connector
The link you set up once between Claude and an account you already have, so Claude can use it while it answers you.
Tool
One named capability the connector opens to Claude. Claude chooses the ones it needs by itself; the directory sheet lists them by name.
Authorization
The service's own sign-in step, where you grant the access Claude will use. Granted once, per person, and taken back the same way.
Approval
The confirmation Claude waits for before doing something that changes an account, shown in the conversation at the right moment.
MCP
The common standard connectors rely on: it is what lets an assistant such as Claude exchange with an outside service like Alma.
Connect

Connect Alma to Claude in three steps

  1. 01

    Locate Alma in Claude

    In Claude's settings, open Customize, then Connectors, and find Alma in the list. On a Team or Enterprise workspace, an Owner or Primary Owner must enable the connector before each member can sign in.

  2. 02

    Launch the connection

    Click Connect on its row, then sign in to Alma in the window Alma opens itself. If the link breaks later, Disconnect and connect again; access can also be removed from the Alma side.

  3. 03

    Check the authorization screen

    Read the authorization screen before you accept. It is Alma's screen, not Claude's, and it sets what the access covers; it may announce more than Claude does day to day, and approval per action stays the default.

Tools

The 5 Alma tools, by what they do

Alma gives Claude 5 tools: 5 that read your account, 0 that change something in it.

All five tools on this sheet read. Alma describes them in a single sentence listing their subjects, without detailing the fields each one returns. Names stay as Claude shows them.

  • 5 read

What Claude reads (5)

5 tools

Five tools that consult your Alma data without changing it.

get_user_profile

Gives Claude access to your Alma profile preferences, so its answers can take into account how you set up the app rather than assume a default eater.

When it helps
you ask for a week of lunch ideas and want them to respect the preferences you already entered in Alma.

Sourcealma.food · October 1, 2026 ↗

get_meal_data

Pulls the meals you logged in Alma into the conversation, which lets Claude reason about what you actually ate instead of what you think you ate.

When it helps
after a tiring week you want Claude to go through what you actually logged before you plan the next one.

Sourcealma.food · October 1, 2026 ↗

get_alma_score_data

Brings in your Alma Score data, the diet quality score the app computes, so Claude can comment on where it stands and how it has moved over time.

When it helps
you changed breakfasts a month ago and want to see whether the score has followed.

Sourcealma.food · October 1, 2026 ↗

get_goals

Lets Claude read the goals you set in Alma, so any suggestion it makes can be checked against your own targets rather than a generic recommendation.

When it helps
you want to know which of your current targets you are closest to reaching this month.

Sourcealma.food · October 1, 2026 ↗

get_weight_history

Retrieves the weight entries Alma holds for you, giving Claude a timeline to put next to your meals and score when you ask about progress.

When it helps
you are following a treatment with your doctor and want a plain summary of the trend before the next appointment.

Sourcealma.food · October 1, 2026 ↗

Approvals

What Claude asks before acting

By default, Claude stops and asks for your confirmation before any action it carries out on an account for you. All five Alma tools only read, and no source says whether a confirmation appears when Claude calls them.

On a Team or Enterprise workspace, owners choose whether members can let some actions go through without a prompt each time. They can also restrict what a connector may do for the whole organisation, keeping reading and closing writing for instance, and nobody bypasses that from a personal account. Claude works with the rights of the person who connected, nothing more: Alma itself says the server is used only after a member authorises access to their own logs.

Plans

Which plans include it

Out of 819 sheets in the official directory, none shows plan availability. That information, connector by connector, is published nowhere: it is a real gap in the catalogue.

The general rule is documented: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organisation before members connect. Alma's own subscription requirement is separate and applies on its side. For the current state, look at the Alma sheet in the directory.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing starts by itself when you log a meal or miss a goal.

A tool list that only reads is an observed floor, not a guarantee: an administrator can open actions no public sheet shows. The verification badge is not a security audit, and Anthropic writes on each sheet that it does not decide which tools a publisher exposes. Everything here comes from Alma's own pages and the directory sheet; no Claude help article covers this connector. To see a connector whose tools do write, the Claude activecampaign connector page is a useful contrast.

Need help

Need help connecting Alma to Claude?

A person reads every message.

FAQ

Claude Alma connector: common questions

01What can Claude do with the Alma connector?
Claude can read your Alma nutrition data and use it to answer you. Its five listed tools cover your logged meals, your Alma Score, your goals, your weight history and your profile preferences. That lets you ask about your real diet, for instance why a week went off track or how close you are to a target, and get an answer built on your own log rather than on general advice. Claude chooses which tools to call by itself.
02Can Claude log meals or change goals in Alma?
Not with the tools listed by default: all five read, and none is documented as writing, sending or deleting. Alma's authorization mentions a write scope next to the read one, yet the publisher only describes read access, and no tool on the sheet uses writing. Treat the list as an observed floor, since an administrator can open actions that appear on no public sheet. For now, logging a meal still happens in the Alma app.
03Does Claude ask before reading my Alma data?
By default Claude asks for confirmation before any action it carries out on an account for you. No source describes a confirmation specific to the five Alma tools, so only that general rule is documented, and every one of them only reads. On a Team or Enterprise workspace, owners decide whether members may let some actions run without a prompt, and they can narrow what the connector is allowed to do for everyone.
04Which Claude plans include the Alma connector?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. Separately, Alma requires its own Premium membership on the Alma side. The directory sheet is the only place showing the connector's current state for you.
05Does Claude see everything in my Alma account?
Claude works with the rights of the person who connected and nothing beyond them. Alma describes its server as member-authorised: you verify your email, then ask about your own food, and access covers your own logs. The documented subjects are meals, Alma Score, goals, weight history and profile. Alma does not list the exact fields each tool returns, so the precise detail Claude sees inside those subjects is not published.
06Why does Alma ask for a Premium membership?
Alma states that its connector requires Alma Premium, which is a subscription to Alma itself, held on the Alma side, not a Claude plan. Without it on the Alma side, connecting does not open your nutrition data to Claude. Alma also explains that there is no public unauthenticated nutrition API and no self-serve key portal, so the member sign-in, with email verification, is the only documented way for Claude to reach your logs.
07Claude or an automation tool for Alma?
They answer different needs, so the choice follows the use, not a ranking. Claude with this connector suits a conversation: you ask about your meals, score or goals and get an explanation built from your own log. An automation tool runs in the background on a trigger or a schedule, without you asking. This connector has no background mode, and nothing happens in Alma until you put a question to Claude.