Curated Finds · Make setup

Get three software finds in Make.

Search our reviewed GitHub tools and Hugging Face models. This on-demand workflow puts up to three matching records in Make, ready for you to inspect.

Each record includes its name and purpose, source and get-software links, category, type, platform and setup requirements, declared licence and licence link, evidence limits and original source-review date. It does not install or run the software it describes.

Current catalogue: 233 records. Latest source review: . Each record keeps its own date.

Set up your own Make workflow

Download the ZIP, extract it and import the blueprint into your Make account. It contains setup instructions and no account credentials. Importing does not start a search.

Use in MakeDownload Make workflow (.zip)

Import and settings checked October 22, 2026 in the publisher’s own account. The original owner workflow returned three records; the fresh import check did not start another run. A separate customer’s connection, payment and results have not been verified.

Before you start

You need your own Make account and an eligible paid Apify account. Open Curated Finds on Apify, sign in and check your account’s payment and usage settings. A website Direct, MCPize, RapidAPI or API.market subscription does not pay for this Apify workflow.

Make’s MCP Client is currently in open beta and included in all Make plans; normal Make credits apply. You do not need an AI module or model prompt. Apify sign-in may request Full API access. Review the permissions before approving: this grants broader account access than this one catalogue, and the selected tool address does not restrict your account’s permissions.

What this search costs

US$0.00599 per completed page, including a valid empty page. A page contains up to 25 records. Asking for three records still uses one completed page.

That is US$5.99 per 1,000 completed pages, with no Actor startup charge, monthly Actor subscription or minimum purchase of 1,000 pages.

The prepared workflow sets a US$0.01 native run event-charge cap for its one page. The cap is a maximum, not the page price. It does not cap your total Apify or Make bill. Your Apify plan, any Apify platform or storage costs, and Make credits or plan charges are separate.

Downloading, copying or importing the workflow does not start the search. Run once starts a potentially billable run. Leave scheduling off and do not add automatic retries or pagination.

Set up, then run once

  1. Copy the scenario or import the blueprint

    Choose Use in Make above, then + Use the scenario to copy the workflow into your own Make account. Or download the ZIP above and extract it. Create a blank scenario in Make, open the scenario menu, choose Import blueprint and select curated-finds-make.json. Keep START-HERE.md open for the field checks.

    Imports start inactive but can default to Every 15 minutes. Change the schedule to On demand and keep it off. If Make asks to activate the scenario, choose Not yet.

  2. Select your connection in both modules

    Create your own Apify OAuth connection in MCP Client → Call a tool. Select that connection in both MCP Client modules; no publisher connection is supplied. Click Save inside the first module, then select the same connection and click Save inside the second module. Save the whole scenario too. If asked to activate it, choose Not yet.

    For this capped workflow, use this exact server address:

    https://mcp.apify.com/?tools=call-actor,get-actor-run,get-dataset-items,get-key-value-store-record

    This address exposes the generic call-actor tool so the workflow can set callOptions.maxTotalChargeUsd to 0.01. Keep its Actor fixed to myworkingmemory/software-library-search. The generic server can also address other Actors your account permits; it is not an account-access boundary.

  3. Check the three-record search and cap

    The first module starts one search with limit=3 and offset=0. Check that its Actor is Curated Finds and its separate callOptions.maxTotalChargeUsd is 0.01. Do not put the cap inside the catalogue search input.

    The second module reads the dataset from that same run. Keep the prepared mappings. Do not add an external destination, schedule, retry or page loop while checking the workflow.

  4. Choose Run once and inspect the result

    Choose Run once manually. Open the module results and check the run status, then the records returned by the dataset module. With the supplied sample search, check for three records. Your own narrower filter may legitimately return fewer records or zero; a valid empty page still costs one page event.

    A success indicator alone is not proof of three useful records. Open the output and inspect the names, links and source-review dates.

  5. Stop and check before another run

    If the run is still in progress, a module fails, or the response is incomplete, inspect that original run in your Apify account. Do not start another search just because a response timed out: the original run may already have been charged.

    This workflow displays records in Make. Sending them to a spreadsheet, email or another app needs your own destination connection and a separate setup check.

Connecting another assistant?

The Actor-only MCP address for other supported clients is different:

https://mcp.apify.com/?tools=myworkingmemory/software-library-search

Use the Claude, Cursor and Codex setup instructions. Do not substitute that address in this capped Make workflow: its dedicated Actor tool does not expose the same explicit cap field. A connection or tool list is not a paid run or a delivery.

Need help?

Keep your scenario off and contact dean@myworkingmemory.ai. Include the step and the visible error, with passwords, tokens and private records removed.

Curated Finds support · Make MCP Client documentation