mothermachine

io.github.Ramp-JetPublished by GitHub account Ramp-Jetv1.1.1Updated Nov 7, 2026

Search a directory of software an agent can adapt or operate, by need, license or interface.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Searches the mothermachine.ai directory of software an agent can adapt or operate, returning ranked listings, full records and the directory's vocabulary.

What you can do
  • Search the directory by need, product to replace, license or interface, with ranked results
  • Read one listing's full record: description, use-when, alternatives, gotchas, accounts, repo, editions and adaptable/operable surface
  • Look up the controlled vocabulary of fields and values to pick valid search filters
When to use it
Useful when a user wants to find software to replace a product, or a tool an agent can adapt or drive through MCP, an API or a CLI, and wants curated details such as license, accounts needed and gotchas before choosing.
Requirements
Runs locally over stdio as the npm package mothermachine with Node 18 or later; no dependencies, accounts, keys or environment variables. It fetches public JSON from mothermachine.ai, so network access is needed.
Before you install
Read-only tools that write no files and send no telemetry; search runs locally so search words are not sent, but requests still reach the site's host like a page visit. Listings are mostly unverified by the curator, so treat verdicts and details as unconfirmed.

Installation

In SourceWeft

  1. Open mothermachine in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mothermachine skill

Search mothermachine.ai, a directory of software an agent can adapt or operate, from a coding agent or an MCP client. This repository is generated from the private source repository on every change to the skill; do not edit it here. Issues and candidate listings go to the site: https://mothermachine.ai/agents.html

Run it

With Node 18 or later, nothing to install:

sh
npx mothermachine "invoicing for a freelancer"

Install the skill

With the skills CLI, into every agent it knows about:

sh
npx skills add Ramp-Jet/mothermachine-skill

Or straight from the site, with no CLI, into Claude Code's skills folder:

sh
for f in SKILL.md scripts/search.mjs scripts/mcp.mjs; do curl -fsSL --create-dirs -o ~/.claude/skills/mothermachine/$f https://mothermachine.ai/skills/mothermachine/$f; done

Then /mothermachine <what you need> searches the directory from the chat.

MCP server

scripts/mcp.mjs is the same search as an MCP server over stdio, with three read-only tools: search, listing, vocab. No dependencies; Node 18 or later.

sh
claude mcp add mothermachine -- npx -y mothermachine mcp

The official MCP Registry lists it as io.github.Ramp-Jet/mothermachine.

If you installed the skill, the server is already on disk:

sh
claude mcp add mothermachine -- node ~/.claude/skills/mothermachine/scripts/mcp.mjs

What it fetches

The skill and the MCP server read the search index and other public JSON files from https://mothermachine.ai. The search runs on your machine, so your search words are not sent. Those requests reach the site's host like any page visit, which the privacy page covers. Neither one writes files or sends telemetry. They run only the scripts in this repository, with Node 18 or later.

What is here

  • SKILL.md: the skill, read by the agent.
  • scripts/search.mjs: the search over the site's index/search.json, also a command line.
  • scripts/mcp.mjs: the MCP server over the same search.
  • scripts/cli.mjs and package.json: the mothermachine command on npm, which runs the two scripts above.
  • scripts/*.test.mjs: tests, run with node --test.
  • .claude-plugin/plugin.json and .mcp.json: the Claude plugin, which is this whole folder.
  • server.json: the listing on the MCP Registry.
  • .github/workflows/: release.yml publishes a new version to npm, and mcp-registry.yml lists it on the MCP Registry.
  • LICENSE: MIT, the same as the source repository.

Everything reads the live site, so an installed copy never goes stale on data; reinstall to pick up changes to the scripts.

Source: README.md at commit fc87d34

Tools

3

listing

Read a listing

The full record for one listing by slug (owner--name, as search returns it): description, use-when list, alternatives, gotchas, accounts needed, the repo with license and stars, editions with how to get each, the adaptable surface (env vars, config files, prompt files, effort), and the operable surface (interface, coverage, reach: what an agent can and cannot do), with confidence per field.

Parametersslugrequired

vocab

Directory vocabulary

The controlled vocabulary the directory is classified with: every field, its values, what each value means, and how many listings carry it. Read it to pick valid filter values for search.

Takes no parameters.

Version history

1
  1. v1.1.1LatestNov 5, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts