Nodebench MCP Server

260 MCP tools across 49 domains. AI Flywheel, quality gates, research, web scraping.

Remote serverstreamable-httpTypeScript

What is the Nodebench MCP server?

260 MCP tools across 49 domains. AI Flywheel, quality gates, research, web scraping. That is what the nodebench mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

NodeBench is a research and reporting product built around five user-facing surfaces:

  • answer-first execution
  • advisor mode by design via dynamic routing:
  • fast executive lane for routine work
  • deeper advisor lane for ambiguity, planning, and harder reasoning
  • similar in spirit to Claude Code's official opusplan split:
  • saved artifacts as first-class objects

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Key — Required
  • GEMINI_API_KEY — Yes
  • LINKUP_API_KEY — Recommended
  • VITE_CONVEX_URL — Yes

What it needs from you

Configuration is passed through the environment: GEMINI_API_KEY, LINKUP_API_KEY, VITE_CONVEX_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Nodebench's toolset — Key, GEMINI_API_KEY, LINKUP_API_KEY and 1 more — is a fair guide to whether it matches your workflow. It is maintained by HomenShum; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Nodebench's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
KeyRequired
GEMINI_API_KEYYes
LINKUP_API_KEYRecommended
VITE_CONVEX_URLYes

How to install the Nodebench MCP server

{
  "mcpServers": {
    "nodebench": {
      "command": "npx",
      "args": ["-y", "nodebench-mcp"],
      "env": {
        "GEMINI_API_KEY": "your-value",
        "LINKUP_API_KEY": "your-value",
        "VITE_CONVEX_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GEMINI_API_KEYCredential the server authenticates with.Yes
LINKUP_API_KEYCredential the server authenticates with.Yes
VITE_CONVEX_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Nodebench to Key.
  • Use Nodebench to GEMINI API KEY.
  • Use Nodebench to LINKUP API KEY.

Frequently asked questions

It connects Nodebench to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Key, GEMINI_API_KEY, LINKUP_API_KEY, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Nodebench directly.