Mealie · OAuth Scopes

Mealie OAuth Scopes

OAuth 2.0 searched

Mealie uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from /api/auth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyRecipesFoodMeal PlanningShopping ListsSelf-HostedOpen-SourceHouseholdNutritionHome Automation
Scopes: 0 Flows: password Method: searched

OAuth endpoints

Token URL
/api/auth/token
Flows
password

Scopes (0)

Mealie implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://docs.mealie.io/documentation/getting-started/authentication/oidc-v2/

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-27'
method: searched
source: https://docs.mealie.io/documentation/getting-started/authentication/oidc-v2/
docs: https://docs.mealie.io/documentation/getting-started/authentication/oidc-v2/
spec_source: openapi/mealie-openapi.json
summary:
  spec_declared_scopes: 0
  note: >-
    The OpenAPI document declares one OAuth2 password flow with an EMPTY scopes
    object — Mealie does not issue scoped access tokens, and an API token carries
    the full permission set of the user who minted it. The scopes recorded below are
    the scopes Mealie requests FROM an external identity provider when it is
    configured as an OIDC relying party; they govern login and group mapping, not
    API authorization. Authorization inside the API is by per-user permission flags
    (see authentication/mealie-authentication.yml).
schemes:
- name: OAuth2PasswordBearer
  source: openapi/mealie-openapi.json
  flows:
  - flow: password
    tokenUrl: /api/auth/token
scopes: []
oidc_relying_party_scopes:
- scope: openid
  required: true
  description: Required by OIDC; identifies the authentication request.
- scope: profile
  required: true
  description: Supplies the display name / username claims used to provision the Mealie user.
- scope: email
  required: true
  description: >-
    Supplies the email claim used to link the IdP identity to a Mealie account, and
    the email_verified claim Mealie requires from v3.21.0 onward.
- scope: groups
  required: false
  description: >-
    Only when group-based access is configured; the actual scope name is whatever
    the OIDC_GROUPS_CLAIM environment variable names.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/mealie-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.