GitMCP for Next.js MCP: what works in Claude, ChatGPT, Cursor, and Grok Bot
GitMCP repo endpoint for vercel/next.js: fetch and search Next.js docs and code. No sign-in needed.
Registry name: (v)
Set it up
URL https://gitmcp.io/vercel/next.js. No sign-in. Paste the URL and it connects. Copy-paste setup: Claude | Claude Code | Cursor | VS Code | ChatGPT
Status grid
| App | Status | Date tested |
|---|---|---|
| Claude | Untested | Not yet tested |
| ChatGPT | Untested | Not yet tested |
| Cursor | Untested | Not yet tested |
| Grok Bot | Untested | Not yet tested |
| MCP Inspector (reference client) | Untested | Not yet tested |
| MCP TypeScript SDK (reference client) | Partial | Fri Oct 16 2026 |
Hands-on test results
| App | Task | Result | Time | Detail | Date tested |
|---|---|---|---|---|---|
| MCP TypeScript SDK (reference client) | connect (no auth) | Works | 975 ms | Connected without sign-in in 975 ms. | Oct 16, 2026, 4:45 PM CT |
| MCP TypeScript SDK (reference client) | list tools | Works | 167 ms | 4 tools: fetch_next_js_documentation, search_next_js_documentation, search_next_js_code, fetch_generic_url_content. | Oct 16, 2026, 4:45 PM CT |
| MCP TypeScript SDK (reference client) | fetch docs (vercel/next.js) | Works | 4477 ms | fetch_next_js_documentation: about 632 KB returned. "# vercel/next.js/docs Documentation Below is a structured llms.txt index of Markdown files extracted from the /docs folder. Each entry conta" | Oct 16, 2026, 4:45 PM CT |
| MCP TypeScript SDK (reference client) | search docs ("generateMetadata") | Works | 19155 ms | search_next_js_documentation: about 20 KB returned. "## Query generateMetadata. ## Response ### Sources: Important: you can fetch the full content of any source using the fetch_url_content tool" | Oct 16, 2026, 4:45 PM CT |
| MCP TypeScript SDK (reference client) | search code ("generateMetadata") | Works | 1872 ms | search_next_js_code: about 13 KB returned. "### Code Search Results for: "generateMetadata" Found 355 matches in vercel/next.js. Page 1 of 12. #### page.tsx - **Path**: examples/with-j" | Oct 16, 2026, 4:45 PM CT |
| MCP TypeScript SDK (reference client) | search docs with nonsense query | Partial | 27066 ms | search_next_js_documentation: about 12 KB returned. "## Query zqxjvflurbo938 qpwmz. ## Response ### Sources: Important: you can fetch the full content of any source using the fetch_url_content " | Oct 16, 2026, 4:45 PM CT |
| MCP TypeScript SDK (reference client) | error handling (missing query) | Works | 235 ms | Protocol error: MCP error -32602: MCP error -32602: Invalid arguments for tool search_next_js_code: [ { "code": "invalid_type", "expected": "string", "received": "undefined", " | Oct 16, 2026, 4:45 PM CT |
Oct 16, 2026, 4:45 PM CT, MCP TypeScript SDK (reference client): Scripted client using the official MCP TypeScript SDK v1.32.1 against https://gitmcp.io/vercel/next.js (Streamable HTTP, protocol 2025-03-26). No sign-in needed. Server speaks the older 2025-03-26 protocol. Server GitMCP v1.1.0. Read-only server, so no create task. 6 of 7 tasks passed.
Automated handshake
No public remote endpoint to check (local or package-only server).
Gotchas
- MCP TypeScript SDK (reference client): fetch_next_js_documentation returned about 632 KB in one call. That will blow past most context windows.
- MCP TypeScript SDK (reference client): Docs search took about 19 s.
- MCP TypeScript SDK (reference client): Code search found 355 matches.
- MCP TypeScript SDK (reference client): A nonsense query took about 27 s and still returned unrelated docs.
Errors and fixes
- MCP tool results too large: context window blown by one call
- MCP tool call times out on slow servers
- MCP search returns results for nonsense queries
FAQ
Does the GitMCP for Next.js MCP server work?
In our hands-on test on Oct 16, 2026, 6 of 7 tasks passed. Main gotcha: fetch_next_js_documentation returned about 632 KB in one call. That will blow past most context windows.
What is the GitMCP for Next.js MCP server URL?
https://gitmcp.io/vercel/next.js (Streamable HTTP).
Does the GitMCP for Next.js MCP server need sign-in?
No sign-in. Paste the URL and it connects.
How do I add the GitMCP for Next.js MCP server to Claude, Cursor, VS Code or ChatGPT?
Follow our copy-paste setup guides: https://connectorreport.com/c/gitmcp-nextjs/setup/claude https://connectorreport.com/c/gitmcp-nextjs/setup/claude-code https://connectorreport.com/c/gitmcp-nextjs/setup/cursor https://connectorreport.com/c/gitmcp-nextjs/setup/vscode https://connectorreport.com/c/gitmcp-nextjs/setup/chatgpt
What errors does the GitMCP for Next.js MCP server give?
MCP tool results too large: context window blown by one call. MCP tool call times out on slow servers. MCP search returns results for nonsense queries.
Compare
- GitMCP for Next.js vs Context7
- GitMCP for Next.js vs OpenAI Docs
- GitMCP for Next.js vs DeepWiki
- GitMCP for Next.js vs Microsoft Learn
- GitMCP for Next.js vs Model Context Protocol Docs
Best MCP servers for documentation and docs search
Compare with other tested connectors | Connector Weather
Request a hands-on test of GitMCP for Next.js
Get the badge
Maintain GitMCP for Next.js or write about it? Show its live ConnectorReport status in your README or docs.
Markdown (README, docs)
[](https://connectorreport.com/c/gitmcp-nextjs?utm_source=badge&utm_medium=embed&utm_campaign=gitmcp-nextjs)
HTML
<a href="https://connectorreport.com/c/gitmcp-nextjs?utm_source=badge&utm_medium=embed&utm_campaign=gitmcp-nextjs"><img src="https://connectorreport.com/badge/gitmcp-nextjs.svg" alt="GitMCP for Next.js MCP status on ConnectorReport"/></a>
The badge updates on its own after every retest. How badges work