# MCP server

Phineus Kitchen runs a Model Context Protocol server so an AI assistant can work with your recipes.

- Endpoint: `https://mcp.kitchen.phineus.ai/mcp` (Streamable HTTP)
- Authentication: `Authorization: Bearer <API token>` on every request. See [Authentication](/help/auth).
  Listing the tools needs no token; calling them does.

## Tools

| Tool | Arguments | What it does |
| --- | --- | --- |
| `search_recipes` | `query` (text), `limit` (1 to 50, default 10) | Search your recipes by name, description or ingredient. |
| `import_recipe_from_url` | `url` | Fetch a recipe page and save it to your kitchen. |
| `add_to_shopping_list` | `item`, `quantity` (default 1), `list_name` (default "Shopping list") | Add an item to a shopping list, creating the list if needed. |

## Try it

```
curl -X POST https://mcp.kitchen.phineus.ai/mcp \
  -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18",
       "capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'
```

Most MCP clients take the URL and a header. For example, as a remote server with a bearer header:

```
{"mcpServers": {"kitchen": {"url": "https://mcp.kitchen.phineus.ai/mcp",
  "headers": {"Authorization": "Bearer <API token>"}}}}
```

The tools call the same REST API described in the [API reference](/help/api-reference), as you.

Phineus Kitchen is a demo product run for testing. Nothing here is real or paid.
