Grumpy Senior Developer MCP

Oh great, a one-liner. How inspiring. Let’s dive into this "masterpiece." 1. **Template Literal Abuse:** Really? A template literal for a static string? Back in my day, we didn't waste resources on unnecessary string interpolation when a plain `'Hello world'` would have done just fine. This reeks of laziness. 2. **Semicolon Missing:** No semicolon at the end of the line? What is this, JavaScript anarchy? Sure, JavaScript allows it, but don’t come crying to me when you run headfirst into an ASI (Automatic Semicolon Insertion) gotcha. 3. **Unnecessary Backticks:** Did I mention how pointless those backticks are? Use them when you actually need variable interpolation or multiline strings, not just to show off that you’re following "modern" syntax trends. 4. **Lack of Context:** What is this accomplishing, exactly? A `"Hello world"` with zero context or an explanation of why it exists? Is this a debugging tool? A placeholder? A cry for help? Back in the old days, we wrote comments. Try it sometime. 5. **Console.log Overkill:** Oh sure, `console.log` is fine **now**, but don't pretend this is production-grade. Professionals use proper logging systems, not this poor man’s debugging trick. **Verdict:** Well, it works, I guess. Next time—if there is a next time—try writing something that doesn’t immediately make me regret my choice of career.

# For VS Code code --add-mcp '{"name":"grumpydev","command":"npx","args":["-y","grumpydev-mcp"]}'

# For VS Code Insiders code-insiders --add-mcp '{"name":"grumpydev","command":"npx","args":["-y","grumpydev-mcp"]}'

{ "servers": { "grumpydev-mcp": { "type": "stdio", "command": "npx", "args": [ "-y", "grumpydev-mcp", ], // Optional, if you want to configure the model // "envFile": "${workspaceFolder}/.env" } } }

{ "mcpServers": { "grumpydev-mcp": { "type": "stdio", "command": "npx", "args": [ "-y", "grumpydev-mcp", ], // Optional, if you want to configure the model // "env": { // "GENAISCRIPT_DEFAULT_MODEL": "<your_model_config>", // } } } }