npm-run-mcp-server
Related Servers
Alternatives to npm-run-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAutomatically generates MCP tools, CLI, and web UI from TypeScript methods, enabling AI agents and chat clients to interact with custom capabilities defined once.95 npm99MIT
- AlicenseNot gradedqualityCmaintenanceUniversal MCP server that wraps any CLI tool, enabling AI assistants to run commands via natural language.MIT
- AlicenseBqualityDmaintenanceExposes Makefile targets as MCP tools, allowing AI agents to execute project automation tasks like build, test, and deploy through natural language.121MIT
- FlicenseBqualityDmaintenanceEnables AI assistants to manage development workflows by running build commands, executing tests, analyzing package.json files, installing dependencies, and performing code linting. Supports multiple package managers (npm, yarn, pnpm) and provides detailed error reporting for development operations.5-
- AlicenseNot gradedqualityAmaintenanceProvides MCP servers that wrap common developer tools (git, npm, docker, etc.) returning structured JSON output, enabling AI agents to reliably interact with these tools without parsing fragile terminal text.4 npm138MIT
- AlicenseNot gradedqualityDmaintenanceExposes Just recipes as MCP tools, allowing AI assistants to discover and execute project commands defined in Justfiles.12 npm1MIT
TDQS
Scored across 5 tools
Each tool corresponds to a distinct npm script (build, prepublishOnly, start, test, test:integration) with no overlap in purpose or description.
Tool names are mostly lowercase but mix single words (build, start, test) and compound names with varying conventions (prepublishonly as one word, test_integration with underscore). A more consistent pattern like 'prepublish_only' would improve clarity.
5 tools is ideal for a focused server designed to run specific npm scripts. Each tool serves a clear purpose without unnecessary clutter.
The server covers the typical lifecycle scripts (build, start, test) and includes integration testing. It may lack common scripts like lint or format, but is sufficient for the stated domain of running predefined npm scripts.