Next Devtools MCP vs Wikipedia Trends MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Next Devtools MCP vs Wikipedia Trends MCP
In-depth architectural comparison of the Next Devtools MCP and Wikipedia Trends MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Next Devtools MCP
Developer Tools · Local stdio
Quality: 84/100 (Excellent) | Auth: No auth required
Wikipedia Trends MCP
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Next Devtools MCP if you need specialized Developer Tools tools running via a local process. Choose Wikipedia Trends MCP if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Next Devtools MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.
Wikipedia page views over time, with growth for any article topic. Free key at trendsmcp.ai
Category & Scope
Tools & Capabilities Breakdown
Next Devtools MCP Tools (4)
nextjs_index
Discover running Next.js dev servers and list each one's runtime MCP tools.
nextjs_call
Call a runtime tool on a discovered server (errors, routes, logs, Server Actions).
nextjs_docs
Gateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
browser_eval
Gateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
Wikipedia Trends MCP Tools (3)
get_time_series
Weekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Wikipedia Trends MCP belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Next Devtools MCP when you need capabilities focused on developer tools and Wikipedia Trends MCP when you require tools for developer tools.
Point-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.
get_top_trends
Live ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).