# Stemma [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://stemma.kitchen/connect/  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/stemma

## Description
Recipes, meal plan, shopping list and pantry from the Stemma iOS app, with per-area OAuth scopes.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Stemma MCP server does

The Stemma MCP server brings four areas from the Stemma iOS app into an MCP-accessible interface: recipes, meal plans, shopping lists, and pantry data. It is intended for an AI client or agent that needs to work with information maintained in Stemma rather than with a separate recipe, grocery, or inventory system.

The available description identifies the data areas but does not specify whether each capability supports reading, writing, searching, or another operation. Treat the listing as confirmation of the supported domains, not as a complete tool reference.

## How it works

Authorization is organized by area. OAuth scopes can be applied separately to recipes, meal plans, shopping lists, and pantry information, so a connected client does not necessarily need access to every category. The Stemma MCP server therefore fits use cases where permissions should be limited according to the data an agent needs.

The supplied material does not describe the OAuth flow, token lifecycle, account linking process, or the names and schemas of individual MCP tools. Those details should be verified before implementation, especially if the client needs to create or change Stemma data rather than only access it.

## Setup and configuration

No installation command, package name, transport, endpoint, environment variable, or client-specific setup is provided in the available material. The source is a Stemma connection page, but its configuration steps are not included here. Use the provider’s connection instructions to determine how an MCP client should authenticate and which OAuth scopes it should request.

When configuring access, select only the Stemma areas required by the workflow. For example, a meal-planning workflow may need recipes and meal plans, while a grocery workflow may need shopping lists and pantry data. The exact scope names are not documented in the listing.

## Tools and capabilities

The documented capability areas are:

- Recipes from the Stemma iOS app
- Meal plans from the Stemma iOS app
- Shopping lists from the Stemma iOS app
- Pantry information from the Stemma iOS app
- Separate OAuth authorization by area

The listing does not provide tool names, parameter definitions, return formats, mutation support, pagination behavior, or synchronization details. Confirm those characteristics before depending on a specific agent workflow. The Stemma MCP server should be evaluated against the required operation for each area, not just the presence of the category name.

## Limitations and notes

The available description is not a full README or API reference. It does not identify supported MCP clients, transport modes, installation requirements, licensing, rate limits, offline behavior, or error handling. It also does not state whether OAuth scopes are mandatory for every area or how an unauthorized request is reported.

The clearest fit is an MCP client that needs scoped access to Stemma’s recipes, meal plans, shopping lists, or pantry data. For production use, obtain the provider’s current setup and tool documentation before selecting scopes or building around unconfirmed read and write behavior.

_Full upstream README: https://allmcps.com/mcp/stemma/readme_