Skip to main content
Glama
136,384 tools. Last updated 2026-05-17 19:19

"Scrapy" matching MCP tools:

  • add_recipe_to_shopping_list

    scraps-kitchen-mcp

    Add all ingredients from a saved recipe to the shopping list. Use when the user wants to shop for a specific recipe. Requires the recipe to have structured ingredient data (most recipes do after enrichment). Get recipe IDs from get_recipes first.
    Connector

  • clear_checked_shopping_items

    scraps-kitchen-mcp

    Remove all checked-off items from the shopping list at once. Use after a shopping trip when the user has bought everything marked. To remove a single item, use remove_shopping_list_item instead.
    Connector

  • remove_shopping_list_item

    scraps-kitchen-mcp

    Permanently remove an item from the shopping list. To remove all checked-off items at once, use clear_checked_shopping_items instead. Get item IDs from get_shopping_list first.
    Connector

  • add_diner

    scraps-kitchen-mcp

    Add a person to the household. Track their allergens, dietary restrictions, preferences, dislikes, goals, and life stage. This data is used for allergen safety and personalized meal suggestions. Only name is required — dietary details can be added later with update_diner.
    Connector

  • rate_recipe_for_diner

    scraps-kitchen-mcp

    Record how a specific household member felt about a recipe. Use to track "who loved it" data, which improves future meal suggestions. Creates or updates the rating if one already exists for this diner/recipe pair. Get recipe IDs from get_recipes and diner IDs from get_household first.
    Connector

  • delete_recipe

    scraps-kitchen-mcp

    Permanently delete a recipe and all associated data (cook notes, diner ratings, image). This cannot be undone. Get recipe IDs from get_recipes first.
    Connector

Matching MCP Servers

  • Scrapy MCP Server

    ThreeFish-AI
    A
    license
    A
    quality
    C
    maintenance
    A powerful web scraping MCP server built on Scrapy and FastMCP that supports multiple scraping methods (HTTP, Scrapy, browser automation), anti-detection techniques, form handling, and concurrent crawling. Designed for commercial environments with enterprise-grade features like intelligent retry mechanisms, performance monitoring, and configurable data extraction.
    Last updated
    10
    3

Matching MCP Connectors

  • scraps-kitchen-mcpOAuth

    Scraps Kitchen gives any AI agent a persistent, household-aware kitchen memory. Unlike generic chatbot recall, Scraps maintains structured cooking data: what's in your fridge (with freshness tracking), who you cook for (with allergens, dietary restrictions, and preferences), your recipe collection (with cook notes and per-diner ratings), your shopping list, and your kitchen equipment. 27 tools across 6 domains let agents read kitchen context, suggest meals that respect dietary safety, update the pantry after cooking, and build a history of what works for your household. Every interaction makes the data richer. Cooking history, preference signals, kitchen awareness = better suggestions next time. All tools work via oAuth and a free scraps.kitchen account.

  • scrapi

    Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.

  • update_recipe

    scraps-kitchen-mcp

    Update a recipe's title, status, rating, favorite, or public sharing status. Use to mark a recipe as cooked, rate it, or toggle favorite. Does not update recipe content — that is managed through the Scraps app. Get recipe IDs from get_recipes first.
    Connector

  • get_recipes

    scraps-kitchen-mcp

    Returns the user's saved recipes with title, status, rating, diet tags, and timestamps. Use to browse what the user has cooked or wants to make. Supports search by keyword and filtering by status or favorites. To get full recipe content and cook notes, use get_recipe with a specific ID.
    Connector

  • suggest_quick_meal

    scraps-kitchen-mcp

    Generate a recipe from a list of ingredients. Returns title, description, estimated time, full recipe markdown, and ingredient list. Use when the user has ingredients and wants a meal idea. No account required. Rate limited to 1 call per IP per 24 hours. Does NOT use the user's pantry or household data — use get_pantry and get_household for personalized context.
    Connector

  • get_household

    scraps-kitchen-mcp

    Returns all household members (diners) with their dietary profiles: allergens, restrictions, preferences, dislikes, goals, and life stages. Use to understand who the user cooks for and what dietary constraints matter. Essential context for safe meal suggestions — check allergens before recommending any recipe.
    Connector

  • remove_pantry_item

    scraps-kitchen-mcp

    Permanently delete a pantry item. Use when the user wants to fully remove an item (not just mark it out of stock — use update_pantry_item with in_stock=false for that). Get item IDs from get_pantry first.
    Connector

  • confirm_pantry_fresh

    scraps-kitchen-mcp

    Reset the staleness clock on pantry items the user confirms are still good. Use when the user says items are fine, or after a pantry check. Get item IDs from get_pantry first.
    Connector

  • get_pantry

    scraps-kitchen-mcp

    Returns the user's pantry items with category, quantity, stock status, perishability, and storage hints. Use when planning meals, checking what ingredients are available, or identifying items that need using up. Set in_stock_only to true (default) to see only available items. Set stale_only to true to see items past their freshness window — useful for "use it up" suggestions.
    Connector

  • update_diner

    scraps-kitchen-mcp

    Update a household member's dietary profile. Array fields (allergens, restrictions, etc.) replace the existing list entirely — send the complete list, not just additions. Get diner IDs from get_household first.
    Connector

  • add_shopping_list_item

    scraps-kitchen-mcp

    Add an item to the shopping list. Use when the user says they need to buy something. To add all ingredients from a recipe at once, use add_recipe_to_shopping_list instead.
    Connector

  • update_pantry_item

    scraps-kitchen-mcp

    Update a pantry item's name, quantity, unit, category, or stock status. Use to correct item details or mark something as out of stock. Get item IDs from get_pantry first.
    Connector

  • add_equipment

    scraps-kitchen-mcp

    Add a piece of kitchen equipment. Equipment context helps tailor recipe suggestions to what the user can actually make. Use when the user mentions having a specific tool.
    Connector

  • get_recipe

    scraps-kitchen-mcp

    Get a single recipe with its full content (ingredients, steps, markdown), cook notes, and ratings. Use when the user wants to cook a specific recipe or see its details. Get recipe IDs from get_recipes first.
    Connector

  • remove_diner

    scraps-kitchen-mcp

    Remove a household member and their dietary profile. This also removes their recipe ratings. Get diner IDs from get_household first.
    Connector

  • mark_ingredients_used

    scraps-kitchen-mcp

    Mark ingredients as consumed after cooking. Matches pantry items by name (fuzzy match). Staples (salt, oil, etc.) are automatically skipped — they don't get depleted. Returns which items were depleted and which were skipped. Use after a cook session to keep the pantry accurate.
    Connector