MCP connector

This repository speaks the Model Context Protocol. Connect it to a Claude project and a conversation can search what is already here and append revisions to it, instead of re-deriving the same recipe every time.

Endpoint

https://noble-notations.ryanjnoble.dev/api/mcp/mcp

The doubled mcp is correct — it is the base path plus the transport segment.

Adding it to claude.ai

Settings → Connectors → Add custom connector.
Paste the endpoint above and connect. Claude registers itself automatically (RFC 7591 dynamic client registration).
You are sent to this site to sign in as the administrator, then shown a consent screen naming exactly what is being granted.
Approve, and the tools appear in your project.

Claude Code and Claude Desktop can use the same endpoint. A Claude Free account cannot add custom connectors.

What it can do

Reading

search_recipes — text, categories, must-include and must-exclude ingredients
get_recipe — the full structured recipe including every revision and its rationale
list_categories, list_ingredients, get_ingredient
list_experiments, get_experiment, get_repository_stats

Writing

create_recipe — a genuinely new dish
revise_recipe — the usual case: append a revision with a rationale
add_note — observations, research with sources, substitutions, warnings
upsert_ingredient — categories, aliases, densities, substitutes
log_experiment — a batch that was actually cooked, with measurements

Safety

Read and write are separate scopes and the consent screen says which is being granted. Nothing is ever deleted or edited in place: a revision is appended and the pointer moves, so every earlier version stays readable at its own URL. Every tool call is written to an audit log.