grumpydev

GrumpyDev MCP server provides an ironic, senior-developer perspective to review code and give pointed feedback. When connected via MCP tooling, it can load and run tools, evaluate code snippets, and return structured responses in the same style as the server’s grumpy persona. Use the provided setup to register the grumpydev-mcp server with your MCP client (VS Code, MCP inspector, or Claude Desktop) and then invoke the server to analyze code blocks or run available tools. The server’s capabilities are designed around generating concise code reviews, highlighting issues, and offering actionable improvements with a sarcastic yet practical tone.

To use it, install the MCP server using the recommended commands (npx or your preferred installer), configure it in your MCP client, and then start a session. Once connected, you can request code reviews, run built-in checks, or leverage any tools exposed by the grumpydev-mcp package. The experience mirrors working with a seasoned teammate who calls out anti-patterns while guiding you toward better coding practices.

Prerequisites:

• Node.js 20 or newer
• npm (installed with Node.js)

Installation options:

1. Quick run (no global install):

   • Ensure Node.js 20+ is installed
   • Run: npx -y grumpydev-mcp
   • This starts the MCP server on-the-fly for immediate use

2. Global installation (preferred for repeated use):

   • Ensure Node.js 20+ is installed
   • Install globally: npm install -g grumpydev-mcp
   • Run: grumpydev-mcp

3. Using through IDE integration (as shown in the README):

   • Follow the in-IDE instructions to add the MCP server with command npx and args -y grumpydev-mcp
   • This configures VS Code or MCP Inspector to connect to the server

Notes:

• If you encounter permission issues on install, consider using a Node version manager or run with appropriate permissions.
• You can also pin to a specific version by using grumpydev-mcp@<version> in the npx command.

Tips and potential issues:

• Environment variables: You can configure model settings via GENAISCRIPT_DEFAULT_MODEL as described in the README. If you customize the model, ensure the required API keys or credentials are available in the environment or envFile.
• Model configuration: Some models may require additional environment variables or credentials; consult GenAIScript configuration docs for details.
• Connectivity: When testing with MCP Inspector or Claude Desktop, ensure the command is set to npx and arguments include -y grumpydev-mcp, and that the server is reachable from your tooling.
• Node version alignment: The project specifies Node.js 20+; using an older Node may lead to compatibility issues with the MCP tooling.
• Updates: If upgrading grumpydev-mcp, verify that changes don’t alter the expected MCP server name/key (grumpydev-mcp) to avoid reconfiguration in clients.