Metmuseum MCP vs Next Devtools MCP

A side-by-side look at the Metmuseum MCP and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Metmuseum MCP logoMetmuseum MCPArt & Culture · Local subprocess (stdio)Metropolitan Museum of Art Collection API integration to search and display artworks in the collection.64GoodAuth: no auth requiredNext Devtools MCP logoNext Devtools MCPDeveloper Tools · Local subprocess (stdio)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.86ExcellentAuth: no auth required

Verdict: choose Metmuseum MCP for art & culture work as a local process; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Metmuseum MCP logoChoose Metmuseum MCP when

  • You need dedicated capabilities in the Art & Culture domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like list-departments, search-museum-objects, get-museum-object.
Explore Metmuseum MCP

Next Devtools MCP logoChoose Next Devtools MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like nextjs_index, nextjs_call, nextjs_docs.
Explore Next Devtools MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMetmuseum MCP logoMetmuseum MCPNext Devtools MCP logoNext Devtools MCP
CategoryArt & CultureDeveloper Tools
Quality signal64/100 · Good86/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars35832
Directory activity 7 views 0 installs 0 upvotes 9 views 0 installs 1 upvotes
Tools44

Tools & capabilities

Metmuseum MCP tools 4

  • list-departmentsList all departments in the Metropolitan Museum of Art (Met Museum)
  • search-museum-objectsSearch for objects in the Metropolitan Museum of Art (Met Museum). Will return Total objects found, followed by a paginated list of Object Ids. If the Met Explorer app (open-met-explorer) is open and the user is referring to its existing results, prefer using those results from context instead of calling this tool. The parameter title should be set to true if you want to search for objects by title. The parameter hasImages is false by default, but can be set to true to return only objects with images. Additional optional filters are available for highlights, tags, on-view status, artist/culture match, medium, geographic location, and date range. Use page and pageSize to paginate results.
  • get-museum-objectGet a museum object by its ID, from the Metropolitan Museum of Art Collection. Use this when the user asks for deeper details on a specific object ID.
  • open-met-explorerOpen the interactive Met Explorer app for browsing and filtering objects. For exploration intents, pass q so the app can run a live search on open. After opening, keep your chat handoff short and UI-focused. For deeper details on a specific object ID, prefer get-museum-object.

Next Devtools MCP tools 4

  • nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.
  • nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).
  • nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
  • browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Metmuseum MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mikechao-metmuseum-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "metmuseum-mcp"
      ]
    }
  }
}

Next Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Metmuseum MCP is categorized under Art & Culture and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Metmuseum MCP for art & culture work and Next Devtools MCP for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Metmuseum MCP is listed as free. Auth: no auth required. Next Devtools MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mikechao-metmuseum-mcp and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Metmuseum MCP has a quality signal of 64/100 (Good) with 7 views, 0 installs and 35 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.