Connect an AI assistant

The Model Context Protocol (MCP) lets an AI assistant work with your recipe collection directly — searching, reading, and with the right token creating, editing and deleting — instead of you copying ingredients back and forth by hand. Rezepte serves an MCP endpoint at https://<your instance>/mcp, and it uses the same credential as the REST API: an API token.

Create a tokenCopy Anchor Link

Follow API tokens to issue one from Settings → API. What the assistant may do follows the Recipes level you choose:

• Read — search and read recipes, their comments and their photos, and list the tags; nothing else.
• Write — also create and edit recipes, star them as favorites, mark them tasty, write comments and add photos.
• Delete — also delete recipes.

Give it the least it needs.

Connect a clientCopy Anchor Link

Once the token is created, its dialog offers two ways to connect, both already filled in with your token and this instance's address — copying them from there is easier than typing them out.

With a commandCopy Anchor Link

Claude Code registers the instance with one command, which the dialog's "Claude Code" tab holds:

claude mcp add --transport http rezepte https://<your instance>/mcp --header "Authorization: Bearer rzp_..."

With a JSON configurationCopy Anchor Link

Most MCP clients, such as Cursor, read an mcpServers block from a configuration file instead, as does a project's .mcp.json. The dialog's "JSON" tab holds this one:

{
  "mcpServers": {
    "rezepte": {
      "type": "http",
      "url": "https://<your instance>/mcp",
      "headers": { "Authorization": "Bearer rzp_..." }
    }
  }
}

VS Code's mcp.json expects the same entry under a top-level servers key instead of mcpServers.

What the assistant can doCopy Anchor Link

Fifteen tools, each reaching as far as the token's scopes allow. The assistant acts as the admin who issued the token, under the same editing rights as in the app:

• Search the collection by keyword, tag, time, favorites or author, and sort it by the most tasty marks.
• Read one recipe in full — ingredients, steps, tags, whether you have starred it, and who marked it tasty.
• List the tags already in use, so it reuses yours instead of inventing new ones.
• Create a recipe.
• Edit a recipe — it replaces the whole document, the same as saving in the editor, including who may edit it.
• Delete a recipe and its photos, with a Delete token only. This cannot be undone.
• Star or unstar a recipe as a favorite.
• Mark a recipe tasty, or take the mark back — never on a recipe the token's admin wrote.
• Read a recipe's comments, and see which ones are new for you — reading it does not clear the dot in the app.
• Write a comment on a recipe, as the token's admin. It cannot edit or delete comments, and photos are not part of it: reading shows only how many photos a comment has.
• Add a photo from a link to a recipe — Rezepte downloads it itself. The first photo a recipe gets becomes its cover.
• Upload photos from your computer, in an assistant that can run commands, such as Claude Code. It asks Rezepte for an upload link that works for 15 minutes and sends each photo there; your token never appears in it. This needs the instance's public address set (REZEPTE_PUBLIC_URL).
• Look at a recipe's photos, to check an upload or describe a dish.

What it cannot doCopy Anchor Link

• It cannot change the cover, reorder or delete photos — do that in the app.
• Photos must be JPEG, PNG or WebP; an assistant converts others, such as iPhone HEIC photos, before uploading.
• It cannot see or add photos on comments.
• It cannot do anything about members, passwords or anyone else's account.
• It can never do more than the token's scopes allow — a Read token cannot create, edit or delete, and only Delete can delete.

Clients that need OAuthCopy Anchor Link

Clients that only connect through OAuth, such as claude.ai's custom connectors, are not supported — Rezepte does not implement OAuth. Every client that accepts a static header works.