Recipe library

What the Recipe library MCP server does

The Recipe library MCP server connects MCP-compatible AI clients to a public collection of recipes for working with personal AI agents. The source library grew from the Israeli Instinct community and contains 29 published recipes in Hebrew, with six of those recipes also available as complete English versions.

Each recipe describes a task-oriented workflow. Depending on the entry, the content can include the intended goal, information to prepare, instructions for the agent, checks for reviewing the result, and limits or open questions reported by the contributor. The collection is useful both for people looking for ideas and for people learning how to formulate a structured request for an AI agent.

The MCP connection is read-only. It provides recipe content as reference data; it does not authorize an agent to send messages, publish content, access accounts, make payments, or carry out other operations described in a recipe.

How it works

The service is available at https://recipes.gitshow.dev/mcp as a public Streamable HTTP endpoint. No API key is required. Configure an MCP client with the endpoint URL, then let the client discover and call the available tools.

The list_recipes tool supports searching the collection and retrieving results in pages. After identifying a relevant entry, call get_recipe with the exact published recipe requested. The retrieval tool supports Hebrew recipes and the full English versions that are available for some entries. Client configuration syntax varies, so the same endpoint may be entered differently depending on the MCP application.

A static API is also available from the project, but the supplied MCP connection is the relevant option when an AI client needs tool-based access.

Setup and configuration

Add the endpoint to an MCP client using a configuration equivalent to:

{
  "mcpServers": {
    "recipe-library": {
      "url": "https://recipes.gitshow.dev/mcp"
    }
  }
}

No environment variables or credentials are specified. The project provides a separate connection guide with client-specific instructions. Because the endpoint is remote and uses Streamable HTTP, verify that the chosen client supports this transport before configuring it.

Tools and capabilities

The Recipe library MCP server exposes two documented tools:

• list_recipes — Searches the recipe collection and supports paging through results.
• get_recipe — Retrieves an exact published recipe in Hebrew, or a full English version when one exists.

The underlying library can be used with Instinct or other agents that have suitable tools. The MCP server itself only supplies recipe information; it does not execute the workflows described in those entries.

Limitations and notes

Recipe coverage is limited to the published collection: 29 Hebrew recipes and six full English companions are stated in the project material. An English translation is not available for every recipe.

The content should be treated as guidance rather than proof that a task will work in a particular environment. Contributor checks and translations do not represent independent, complete execution testing. Review each recipe, adapt its details, define permissions, and inspect the result before relying on it.

The endpoint is read-only, and no authentication is required. That makes it suitable for retrieval but does not make the recipe instructions inherently safe to execute. Actions involving communication, publication, accounts, or payments require separate approval outside this MCP connection.