Developers & AI Agents

Hungry Goblin exposes a scoped OAuth 2.1 API for AI assistants via the Model Context Protocol (MCP). No contact-sales flow — create a free account, connect Claude or ChatGPT, and authorize least-privilege scopes.

Quick links

• OpenAPI specification (YAML)
• API index (JSON)
• MCP manifest (JSON)
• OAuth authorization server metadata
• Protected resource metadata (scopes_supported)
• Connect to Claude / ChatGPT
• llms.txt — agent when-to-use guidance

Authentication

OAuth 2.1 with PKCE (S256) is required. Dynamic Client Registration is supported at https://zonykdtrkbptszqellsn.supabase.co/functions/v1/oauth-server/register — agents can self-register without manual API keys. Human users can also sign up free and connect MCP from the app.

OAuth scopes

• recipes:read — view recipes
• recipes:write — create and edit recipes
• recipes:delete — delete recipes
• history:read — view cooking history
• history:write — log cooked meals
• history:delete — delete history entries
• suggestions:read — get meal suggestions
• search:read — search recipes
• offline_access — refresh tokens

MCP tools

POST JSON-RPC 2.0 to /mcp (Streamable HTTP). Tools include list_recipes, get_recipe, create_recipe, update_recipe, delete_recipe, get_meal_suggestion, log_cooked_meal, get_cooking_history, delete_history_entry, and search_recipes. Each tool requires the scopes listed in openapi.json.

JSON error responses

All API and MCP errors return structured JSON — never HTML. Example 404 for unknown API paths:

{
  "error": "not_found",
  "error_description": "The requested resource does not exist.",
  "code": 404,
  "documentation": "https://hungrygoblin.com/developers#errors",
  "hint": "See /openapi.json for the full API surface."
}

MCP JSON-RPC errors use { "jsonrpc": "2.0", "id": ..., "error": { "code": ..., "message": ... } }.

Self-serve onboarding

Free tier: sign up at /auth, no credit card. Sandbox: your own account data, scoped by OAuth. MCP setup instructions at /connect.