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.
git clone --depth 1 https://github.com/shuchitajain/awesome-ai-setupWrote 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/agents/shuchitajain/awesome-ai-setup/generate-mcp-config)<a href="https://agentmods.dev/agents/shuchitajain/awesome-ai-setup/generate-mcp-config"><img src="https://agentmods.dev/badge/agents/shuchitajain/awesome-ai-setup/generate-mcp-config/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/shuchitajain/awesome-ai-setup/generate-mcp-config"><img src="https://agentmods.dev/badge/agents/shuchitajain/awesome-ai-setup/generate-mcp-config.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00019 | $0.01382 |
| Opus 5 | $0.00010 | $0.00691 |
| Sonnet 5 | $0.00004 | $0.00276 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
generate-mcp-config 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 10d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Generate MCP Configuration
You are generating MCP (Model Context Protocol) configuration files for this repository.
MCP connects AI tools to live data sources - your database schema, GitHub issues, filesystem, and external APIs - so they work with real state instead of documented state. This agent detects which integrations are relevant for this project and generates the correct config file for each AI tool in use.
Step 1 - Detect the Stack and Existing Setup
Read these sources:
- Dependency manifest (
pubspec.yaml,package.json,Cargo.toml, etc.) - identify the tech stack and any backend services in use (Supabase, Firebase, PostgreSQL, etc.) - Existing MCP configs - check for
.mcp.json,.cursor/mcp.json,.vscode/mcp.json. Read them if present - don't overwrite entries that already exist. - Environment files - check
.env.exampleor.env(keys only, never values) to understand what external services are configured - README or docs - may name backend services explicitly
Identify which AI tools are in use by checking for:
CLAUDE.md→ Claude Code → config goes in.mcp.json.cursor/or.cursorrules→ Cursor → config goes in.cursor/mcp.json.github/copilot-instructions.md→ GitHub Copilot → config goes in.vscode/mcp.json
If none are detected, generate all three.
Step 2 - Select Relevant MCP Servers
Based on what you found, select from these servers. Only include servers with a clear reason to exist in this project.
Universal (include for any project):
| Server | npm package | When to include |
|---|---|---|
| GitHub | @modelcontextprotocol/server-github |
Any project with a GitHub remote |
| Filesystem | @modelcontextprotocol/server-filesystem |
Always - lets AI read actual files |
Database / backend:
| Server | npm package | When to include |
|---|---|---|
| PostgreSQL | @modelcontextprotocol/server-postgres |
If pg, postgres, drizzle-orm, or prisma detected |
| Supabase | @supabase/mcp-server-supabase |
If @supabase/supabase-js detected |
| Firebase | mcp-server-firebase |
If firebase or firebase-admin detected |
| SQLite | @modelcontextprotocol/server-sqlite |
If sqlite3, better-sqlite3, or sqflite detected |
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.
- 10d ago First seen · 156 lines · 19 tokens per session scan A a0be212735b3
generate-mcp-config is an agent published in the GitHub repository shuchitajain/awesome-ai-setup (5 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,382 once invoked, about $0.0001 per session on Opus 5. 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 agents, from other repositories
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.