Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/mars-mx/vibesaas/mcp-setupgit clone --depth 1 https://github.com/mars-mx/vibesaasWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/mars-mx/vibesaas/mcp-setup)<a href="https://agentmods.dev/commands/mars-mx/vibesaas/mcp-setup"><img src="https://agentmods.dev/badge/commands/mars-mx/vibesaas/mcp-setup.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01287 |
| Opus 5 | $0.00000 | $0.00643 |
| Sonnet 5 | $0.00000 | $0.00257 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
mcp-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Setup Command
You are tasked with setting up MCP (Model Context Protocol) servers for the user. Follow these steps to configure the required servers.
Required MCP Servers
-
Upstash Context7 MCP - Enhanced context management
-
Zilliz Claude Context - Vector database integration for context retrieval
-
Sequential Thinking Server - Structured problem-solving capabilities
Setup Instructions for Claude
When the user requests MCP setup, follow these steps:
Step 1: Verify Prerequisites
- Check if Node.js is installed:
node --version - Check if npm is available:
npm --version - Inform the user they need a Smithery account at https://smithery.ai
Step 2: Guide User to Obtain API Keys
Tell the user they need to:
-
Smithery API Key (required for Smithery servers):
- Navigate to https://smithery.ai
- Create an account or log in
- Go to profile/API settings to get their API key
-
Upstash Credentials (for Context7):
- Visit https://console.upstash.com
- Create a Redis database
- Obtain REST URL and REST Token
-
Zilliz Credentials (for Claude Context):
- Visit https://cloud.zilliz.com
- Create a cluster
- Generate API credentials and note the endpoint
Step 3: Install MCP Servers via Smithery CLI
Use the Smithery CLI with proper authentication. The user will need to provide their Smithery profile and key:
# Install Sequential Thinking Server
echo "n" | npx -y @smithery/cli@latest install @smithery-ai/server-sequential-thinking \
--client claude \
--profile <user-profile> \
--key <smithery-api-key>
# Install Upstash Context7 MCP
echo "n" | npx -y @smithery/cli@latest install @upstash/context7-mcp \
--client claude \
--profile <user-profile> \
--key <smithery-api-key>
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 146 lines · 0 tokens per session scan A 2c43dec5e721
mcp-setup is a command published in the GitHub repository mars-mx/vibesaas (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,287 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.