What is the main functional difference between Yeelight Metadata MCP Server and Next Devtools MCP?

Yeelight Metadata MCP Server is categorized under Developer Tools and uses a remote HTTP/SSE transport. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Yeelight Metadata MCP Server for developer tools work and Next Devtools MCP for developer tools.

How do I install Yeelight Metadata MCP Server or Next Devtools MCP in Claude Desktop, Cursor, or Windsurf?

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.

Are Yeelight Metadata MCP Server and Next Devtools MCP free to use, or do they require API keys?

Yeelight Metadata MCP Server has no declared pricing — check the project's own site. 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.

Can I run both Yeelight Metadata MCP Server and Next Devtools MCP at the same time in my AI client?

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

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Yeelight Metadata MCP Server has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 8 views, 0 installs and 828 GitHub stars.

Yeelight Metadata MCP Server vs Next Devtools MCP

A side-by-side look at the Yeelight Metadata MCP Server 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.

Yeelight Metadata MCP ServerDeveloper Tools · Remote HTTP/SSEYeelight home metadata and guarded management workflows.36FairAuth: not declared

Next 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 Yeelight Metadata MCP Server for developer tools work over a hosted endpoint; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Spec	Y Yeelight Metadata MCP Server	Next Devtools MCP
Category	Developer Tools	Developer Tools
Quality signal	36/100 · Fair	86/100 · Excellent
Install command	Confirmed	Confirmed
Transport	Remote HTTP/SSE	Local subprocess (stdio)
Auth	Not declared	No auth required
Pricing	Not declared	Free
Required env vars	`METADATA_MCP_RUNTIME_ENVMETADATA_MCP_BIND_HOSTMETADATA_MCP_PORTMETADATA_MCP_PATHMETADATA_MCP_DEFAULT_REGION`	None listed
Verified owner	Community listing	Verified
GitHub stars	0	828
Directory activity	0 views 0 installs 0 upvotes	8 views 0 installs 1 upvotes
Tools	Not listed	4
Full listing	View Yeelight Metadata MCP Server	View Next Devtools MCP

Yeelight Metadata MCP Server vs Next Devtools MCP

Which MCP server should you choose?

Y
Choose Yeelight Metadata MCP Server when

Choose Next Devtools MCP when

Feature & specification comparison

Tools & capabilities

Yeelight Metadata MCP Server tools

Next Devtools MCP tools 4

Ready-to-paste client configs