SaaS Puppy MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (used with --http mode). | 8080 |
| SAAS_PUPPY_MCP_URL | No | Upstream public MCP endpoint address. Must use https (plain http is accepted only for localhost, for development). | https://saaspuppy.com/MCP |
| SAAS_PUPPY_MCP_TIMEOUT_MS | No | Upstream timeout in milliseconds. | 20000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_toolsA | 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. |
| compare_toolsA | Compare short purpose, quota, pros, cons and catch summaries for two or three tools in one category; full details remain on SaaS Puppy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
list_tools and compare_tools have clearly different intents: one surfaces names/examples, the other produces a structured comparison. The boundary is understandable, though both operate on the same narrow data and could blur if a user wants both listing and comparison in one step.
Both tools follow a clean verb_noun snake_case pattern (list_tools, compare_tools). With only two tools, the convention is fully consistent and predictable.
Two tools is thin for a SaaS tool directory/comparison server; the surface feels like a minimal preview rather than a usable toolkit. It is not egregiously over-scoped, but the small count limits what an agent can accomplish without leaving the MCP.
There is no way to retrieve full tool records, search by name or use case, or enumerate categories systematically—list_tools explicitly refuses bulk exports and pagination. The server depends on external browsing for detailed data, leaving significant gaps for an agent trying to answer tool-selection questions end-to-end.