Issues with `nextjs_docs` and `nextjs-docs://llms-index`

Thinking: Attempting to access Next.js docs
I’m trying to read the required nextjs-docs://llms-index resource via the read tool to comply with documentation access requirements, but previous attempts failed; I’ll retry
reading it directly to resolve this blocker before proceeding.

→ Read nextjs-docs://llms-index
Error: ENOENT: no such file or directory, scandir '<project_path>/nextjs-docs:' • biome

Thinking: Blocking on Next.js docs access

The Next.js docs tool and path access failed, so I can't retrieve necessary docs to proceed. I'll ask the user to confirm or provide access to the Next.js docs, then continue with non-blocked planning.

Blocker: the mandatory Next.js docs index isn’t accessible right now. I tried nextjs-docs://llms-index via the docs tool and Read, but both failed.

Me: Fetch the next-devtools-mcp README at https://raw.githubusercontent.com/vercel/next-devtools-mcp/refs/heads/main/README.md and tell me what you're having issues with.

% WebFetch https://raw.githubusercontent.com/vercel/next-devtools-mcp/refs/heads/main/README.md

Thinking: Highlighting docs tool usage mismatch

The main issue is that the tool was used with a nonexistent llms-index path, while the README specifies using nextjs_docs with action=search or get and a query instead of a
path. The init guidance demanding llms-index conflicts with this, causing fetch failures and NOT_FOUND errors; updating usage to align with README actions is needed.

Thinking: Detailing docs tool schema and usage conflicts

The nextjs_docs tool signature accepts only path and anchor, but the README requires action=search or get with queries, creating a schema mismatch. Also, the init step’s demand
to read nextjs-docs://llms-index is outdated and causes fetch failures and NOT_FOUND errors, since that resource doesn't exist. To fix this, updating to the latest MCP version
supporting search actions and verifying tool config and environment are recommended.

Here’s what I’m seeing from the README vs. what actually happened:

• The README says nextjs_docs is a two‑step tool (action: "search" then action: "get"). Our tool interface only accepts path/anchor, so it can’t run the documented search
  workflow.
• The README does not mention a nextjs-docs://llms-index resource. The only listed resources are cache-components://…, nextjs16://…, and nextjs-fundamentals://…. That makes the
  init requirement to read nextjs-docs://llms-index look outdated.
• Calls I tried:
  • nextjs_docs with path: "/llms-index" → NOT_FOUND
  • nextjs_docs with path: "nextjs-docs://llms-index" → fetch failed
  • Reading nextjs-docs://llms-index via Read → ENOENT (expected: Read can’t access MCP resources)

So the issue is a mismatch between the init tool’s enforced workflow and the current MCP server/README behavior.

nextjs_docs only accepts { path, anchor } and requires nextjs-docs://llms-index, but that MCP resource is not accessible here. The README still documents a search/get API that does not match the tool schema.

Repro

1. nextjs_docs({ action: "search", query: "generateMetadata", routerType: "app" }) -> Missing required argument: path
2. nextjs_docs({ path: "/llms-index" }) -> NOT_FOUND (instructs to read nextjs-docs://llms-index)
3. nextjs_docs({ path: "nextjs-docs://llms-index" }) -> fetch failed

Expected

Either the nextjs-docs://llms-index resource is available, or nextjs_docs supports the README search/get workflow.

Actual

Tool requires a path but the index resource is unreachable, so docs lookup is blocked.

Code reference

src/tools/nextjs-docs.ts defines path-only input and hard-depends on nextjs-docs://llms-index.