Paprika Recipe Nexus Adapter

A service adhering to the Model Context Protocol (MCP) specification. It surfaces your stored Paprika 3 culinary records as accessible resources for cognitive agents like Claude, and conversely, permits such agents to initiate new recipes or revise extant ones in your Paprika application.

🖼️ Operational Visualization

✨ Core Capabilities

Encountering a functional gap? Please submit a feature request via an issue report on this repository!

🗄️ Available Data Assets

• Primary Recipes (Complete) ✅
• Recipe Photographic Assets (Under Development) 🚧

⚙️ Executable Functions

• initiate_paprika_cookbook_entry
  Grants the LLM authorization to commit a novel recipe document into your Paprika application suite.
• revise_paprika_cookbook_entry
  Empowers the LLM to apply modifications to a pre-existing recipe record.

💾 Prerequisites for Deployment

• ✅ A computational environment running macOS, Linux, or Windows.
• ✅ An active installation of Paprika 3 configured for synchronized cloud backup.
• ✅ Valid Paprika 3 credentials (user identification and access key).
• ✅ An LLM client (e.g., Claude) featuring active MCP tool integration capabilities.

🚀 Setup & Deployment

You may acquire a pre-compiled executable from the project's Release Artifacts page.

🍎 macOS Installation via Homebrew

For macOS users, installation is streamlined using Homebrew:

brew tap soggycactus/tap
brew install paprika-3-mcp

🐧 Linux / 🪟 Windows Deployment

1. Navigate to the most recent version artifacts.
2. Retrieve the compressed package corresponding to your OS and hardware architecture:
3. Linux users: paprika-3-mcp_<version>_linux_amd64.zip
4. Windows users: paprika-3-mcp_<version>_windows_amd64.zip
5. Decompress the archive:
6. Linux: bash unzip paprika-3-mcp_<version>_<os>_<arch>.zip
7. Windows:
   • Utilize the built-in "Extract All" function, or employ a third-party utility such as 7-Zip.

8. Relocate the executable file to a directory indexed in your system's PATH environment variable:

9. Linux:

   bash sudo mv paprika-3-mcp /usr/local/bin/

10. Windows:

    • Place paprika-3-mcp.exe within a PATH-accessible folder (e.g., %USERPROFILE%\bin).

✅ Verifying Successful Initialization

Confirm the installation integrity by querying the version number:

paprika-3-mcp --version

Expected Output:

paprika-3-mcp version v0.1.0

🧠 Configuring Claude Integration

If this is your initial MCP deployment, consult the MCP Quickstart Guide for setting up the Claude Desktop client and establishing the necessary server linkage.

To integrate paprika-3-mcp into Claude, append a new configuration block within the mcpServers segment of your claude_desktop_config.json file:

{
  "mcpServers": {
    "paprika-3": {
      "command": "paprika-3-mcp",
      "args": [
        "--username",
        "<your paprika 3 email/identifier>",
        "--password",
        "<your paprika 3 secret>"
      ]
    }
  }
}

Upon restarting Claude, the new tools should become accessible via the dedicated instrumentation icon (resembling a hammerhead):

📄 Licensing Information

This intellectual property is made available under the terms of the MIT License © 2025 Lucas Stephens.

---

🗂️ Supplementary Data

📄 Accessing Service Diagnostic Streams

The MCP gateway records structured diagnostics utilizing Go's slog, incorporating log rotation via lumberjack. Log files are automatically positioned according to the host OS:

Operating System	Log File Location
macOS	~/Library/Logs/paprika-3-mcp/server.log
Linux	/var/log/paprika-3-mcp/server.log
Windows	%APPDATA%\paprika-3-mcp\server.log
Unspecified	/tmp/paprika-3-mcp/server.log

💡 Retention Policy: Logs undergo automatic truncation when reaching 100MB, preserving a maximum of 5 prior backup files. All log entries are purged after a 10-day interval.