Nodebench
Attach a large local MCP toolbox—research, scraping, quality gates, and flywheel helpers—so one agent install covers many Build and Ship tasks.
Overview
Nodebench is an MCP server for the Build phase that provides 260 local tools across 49 domains for research, scraping, quality gates, and agent flywheel workflows.
What is this MCP server?
- 260 MCP tools organized across 49 domains in one npm stdio server
- Includes AI Flywheel utilities, quality gates, research, and web scraping clusters
- Local nodebench-mcp package (v2.31.2) from packages/mcp-local monorepo
- Suited as a swiss-army MCP layer instead of installing dozens of single-purpose servers
- Intermediate setup: broader surface area implies selective tool allowlisting
- 49 tool domains
- Package version 2.31.2 via npm identifier nodebench-mcp
What problem does it solve?
Solo builders hit a wall installing and maintaining many one-off MCP servers for research, scraping, and QA tasks.
Who is it for?
Power users who want a consolidated local MCP bench and are willing to curate which of 260 tools each project exposes.
Skip if: Beginners who need one clear integration with minimal configuration and predictable tool count.
What do I get? / Deliverables
One stdio MCP install gives your agent a broad toolkit you can phase-enable as the product moves from research to ship.
- Access to 260 MCP tools across 49 domains from one server
- Research and scraping calls without separate MCP installs
- Optional quality-gate checks during build and ship loops
Recommended MCP Servers
Journey fit
Nodebench first appears when builders equip agents with tooling, but its 49-domain surface spans research through validation across the solo journey. Agent-tooling is the canonical shelf for multi-domain stdio MCP servers that extend what Claude Code and Cursor can do in one package.
How it compares
Multi-domain local MCP toolkit, not a hosted single-API rental or webhook-audit specialist.
Common Questions / FAQ
Who is Nodebench for?
Indie agent builders who want research, scraping, quality gates, and automation in one Node-based stdio MCP server instead of many tiny plugins.
When should I use Nodebench?
Use it when equipping your agent during Build and reuse subsets for Idea research, Ship QA, or Grow content gathering as the project matures.
How do I add Nodebench to my agent?
Install the nodebench-mcp npm package, register the stdio server in your MCP client config, and start with an allowlisted subset of tools for your repo.