Remote connector

Spoonjoy MCP

Spoonjoy MCP gives an authorized agent tools for kitchen work that is too detailed for ordinary app clicks: creating recipes, importing from messy sources, reshaping cookbooks, and updating your shopping list.

Developer Platform Sign In

TL;DR

Use the app for easy things like finding and following recipes. Use an agent through MCP when the work becomes multi-step: turn a page, photo, or notes into a structured Spoonjoy recipe, revise it, organize it, and make the shopping-list changes around it. The middle eventually wants generative UI; for now, MCP is the agent lane.

Where MCP Fits

Easy

Use the app

Find, follow, spoon, and cook recipes directly in Spoonjoy. Browsing should stay fast, visual, and under your hands.

Middle

Generative UI later

Planning, guided editing, and review will eventually want UI that forms around the task. That layer is not here yet.

Complex

Use an agent

Author or import recipes from messy sources, normalize ingredients and steps, reorganize cookbooks, and make scoped list changes.

Owner-scopedOAuth protectedStreamable HTTP

The browser page is the guide. The protocol call is authenticated POST JSON-RPC.

Visiting this URL shows setup help. MCP is not a better way to browse Spoonjoy; it is the bridge for agent work where reading, transforming, and writing structured kitchen data belong together. MCP clients send JSON-RPC to the same URL with POST; every request, including initialize, needs a valid bearer token or an OAuth access token bound to this resource.

https://spoonjoy-v2.mendelow-studio.workers.dev/mcp

Endpoint: POST /mcp
Transport: Streamable HTTP, stateless
Payload: JSON-RPC initialize, tools/list, tools/call
Auth: Authorization: Bearer on every request
Streaming: no SSE, no batching

What It Can Use

Import through an agent

Let an agent read a source you provide, interpret the recipe, and call create_recipe with structured steps, ingredients, images, and source notes.

Author real recipes

Draft, revise, fork, delete, spoon, and upload user-provided images through the same operation layer the app uses.

Organize cookbooks

Create collections, inspect cookbook contents, and add or remove recipes when the organization work gets too fiddly for clicks.

Manage the shopping list

Turn meal decisions into owner-scoped shopping-list changes from the agent you authorize.

MCP deliberately has no arbitrary URL import tool. For imports, let the agent read the source you provide and create structured Spoonjoy data through create_recipe. AI cover generation also stays out of MCP. For broader REST and OpenAPI access, use the API guide.

How To Connect

Use OAuth when the agent supports it

claude.ai, Claude Desktop, and similar MCP clients can discover Spoonjoy auth from the endpoint challenge, then send you through normal sign-in and consent.

Use a bearer token for Claude Code

Create an owner-scoped Spoonjoy token, store it like a password, then pass it as an Authorization header when adding the remote MCP server.

Give the agent the smallest useful scope

Kitchen scopes unlock recipe and cookbook writes. Shopping-list-only agents can use shopping-list scopes. Token lifecycle tools require token scopes.

Claude Code

After you create a Spoonjoy token, add the remote server with an explicit bearer header:

TOKEN=sj_your_token_here
claude mcp add --transport http \
  spoonjoy \
  https://spoonjoy.app/mcp \
  --header "Authorization: Bearer $TOKEN"