ref-tools-mcp and next-devtools-mcp
These tools are complements: "ref-tools/ref-tools-mcp" provides general assistance for coding agents working with libraries, while "vercel/next-devtools-mcp" offers specific Next.js development tools for those agents, allowing for a combined approach to error reduction and framework-specific development.
About ref-tools-mcp
ref-tools/ref-tools-mcp
Helping coding agents never make mistakes working with public or private libraries without wasting the context window.
Implements an MCP server with two tools—semantic search and URL fetching—that intelligently filters documentation results based on session search history to return only the most contextually relevant sections, typically 5k tokens maximum. Uses adaptive multi-step search patterns where agents refine queries based on intermediate results, avoiding the token waste of traditional pagination and over-fetching. Designed for integration with Claude Code, Cursor, and OpenAI deep research, with both HTTP (recommended) and stdio transport options.
About next-devtools-mcp
vercel/next-devtools-mcp
Next.js Development for Coding Agent
Implements a Model Context Protocol (MCP) server that bridges coding agents (Claude, Cursor, Gemini, etc.) with Next.js development through runtime diagnostics and automated tooling. For Next.js 16+, it auto-discovers the dev server at `http://localhost:3000/_next/mcp` and provides real-time access to application errors, route structure, and server logs via `nextjs_index` and `nextjs_call` tools. Includes modular knowledge base resources covering Cache Components, migrations, and fundamentals, with single-command installation via `add-mcp` across multiple agent platforms.
Scores updated daily from GitHub, PyPI, and npm data. How scores work