io.github.rahulparathyPublished by GitHub account rahulparathyv0.1.0Updated Oct 31, 2026
Look up or compare free-tier developer tools, with the catch spelled out.
Lets an assistant look up or compare free-tier developer tools from the SaaS Puppy directory, including each tool's free plan and its catch.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.rahulparathy%2Fsaas-puppy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"saas-puppy": {
"type": "http",
"url": "https://saaspuppy.com/MCP"
}
}
}[SaaS Puppy MCP: ask your AI about free-tier developer tools]
[CI] [License: MIT] [Node 20 or newer] [MCP server]
Let your AI assistant look things up in SaaS Puppy, a directory of free-tier developer tools.
Ask it about one tool, or have it compare two or three. For each one you get what the free plan includes, the good and bad points, and the catch, plus a link to the full listing.
MCP (Model Context Protocol) is a standard way to plug extra abilities into an AI assistant. Think of it as a power adapter: once this one is plugged in, your assistant can check SaaS Puppy for you instead of guessing from memory.
After you connect it, ask in plain language:
The assistant picks the right tool and shows you the answer. You never call the tools yourself.
Pick the way that matches your app. The first is the easiest because there is nothing to install.
Use this address, with no authentication:
More apps (Hermes Agent, OpenClaw and others) are in docs/clients.md. App menus change often, so if a step looks different, follow the app's own MCP help and use the address above.
Some apps only support local servers. For those, install Node.js (version 20 or newer), then add this to the app's MCP settings:
For Claude Code: claude mcp add saas-puppy -- npx -y saas-puppy-mcp
On your computer, run:
You should see:
If a line says FAIL, it also tells you what to try next.
Is it really free? Yes. There is no account, key or limit you need to manage. The hosted address is shared, so it has fair-use limits and may slow down if someone sends too many requests.
Does it see my files or chats? No. It only receives the lookup your assistant sends (for example, "Neon") and returns an answer. It holds no keys, reads no files and has no analytics of its own.
Why won't it list every tool? On purpose. The full directory is on saaspuppy.com. The assistant can look up one tool, a few examples from one category, or compare two or three tools. It declines requests to dump or page through everything.
What does "temporarily unavailable" mean? The package could not reach saaspuppy.com. Wait a minute and ask again. If it keeps happening, run the check above.
Where does the data come from? From the live SaaS Puppy directory. Each answer includes the date the listing was last verified. Prices and limits change, so open the linked page before you rely on a number.
npx says "command not found". Install Node.js from nodejs.org (the LTS version is fine), then restart your app.
Something else is wrong. Open an issue and paste the output of --check.
Each summary has the tool's purpose, up to three good things and three bad things, the catch, a free-tier summary, pricing models, trial days, whether a card is required, the date it was last verified, and the SaaS Puppy page URL.
This package is a small proxy. It defines the two tools locally, with the same names, input schemas and instructions as the hosted public MCP, so clients and registries can list them without a network call. When a tool runs, the package forwards the request to the hosted endpoint and returns the answer.
The HTTP mode is stateless, so it runs behind any load balancer. A Dockerfile is included:
The upstream address must use https. Plain http is accepted only for localhost, for development.
The tests run a mock of the hosted endpoint, so they need no network.
See CONTRIBUTING.md to send a change.
Maintainers: docs/launch-guide.md is a step-by-step launch checklist in plain English, and docs/publishing.md has the registry details.
MIT. SaaS Puppy listing data belongs to SaaS Puppy and is served under the terms at saaspuppy.com.
Source: README.md at commit cb8355e
Summarize a tool or category
Summarize one exact tool name or slug, or up to three examples from a specific category. No bulk exports, pagination or full records; visit SaaS Puppy for more.
querycategorypricing_modelsCompare tool summaries
Compare short purpose, quota, pros, cons and catch summaries for two or three tools in one category; full details remain on SaaS Puppy.
slugsrequired100% 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.
https://saaspuppy.com/MCP{ "mcpServers": { "saas-puppy": { "command": "npx", "args": ["-y", "saas-puppy-mcp"] } }}npx -y saas-puppy-mcp --checkChecking the SaaS Puppy MCP at https://saaspuppy.com/MCP
PASS Connected to the directory.PASS Found both tools: list_tools and compare_tools.PASS Asked a test question and got an answer.
All good. Your AI app can use this server.npx -y saas-puppy-mcp # stdio (default)npx -y saas-puppy-mcp --http --port 8080 # Streamable HTTP at /mcp, health check at /healthznpx -y saas-puppy-mcp --check # self-testdocker build -t saas-puppy-mcp .docker run --rm -p 8080:8080 saas-puppy-mcpnpm installnpm run check # typecheck, build and test in one go