Next Devtools MCP vs Yeelight Metadata MCP Server
A side-by-side look at the Next Devtools MCP and Yeelight Metadata MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Y
Yeelight Metadata MCP ServerDeveloper Tools · Remote HTTP/SSEYeelight home metadata and guarded management workflows.36FairAuth: not declaredVerdict: choose Next Devtools MCP for developer tools work as a local process; choose Yeelight Metadata MCP Server for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
YChoose Yeelight Metadata MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
METADATA_MCP_RUNTIME_ENV, METADATA_MCP_BIND_HOST, METADATA_MCP_PORT, METADATA_MCP_PATH, METADATA_MCP_DEFAULT_REGION.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Y Yeelight Metadata MCP Server | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 86/100 · Excellent | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | METADATA_MCP_RUNTIME_ENVMETADATA_MCP_BIND_HOSTMETADATA_MCP_PORTMETADATA_MCP_PATHMETADATA_MCP_DEFAULT_REGION |
| Verified owner | Verified | Community listing |
| GitHub stars | 828 | 0 |
| Directory activity | 8 views 0 installs 1 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Next Devtools MCP | View Yeelight Metadata MCP Server |
Tools & capabilities
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.
Yeelight Metadata MCP Server tools
No tool names declared yet. Check the project README from the listing page.
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.
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Yeelight Metadata MCP Server
{
"mcpServers": {
"yeelight-metadata-mcp-server": {
"url": "https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp"
}
}
}
Frequently asked questions
Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. Yeelight Metadata MCP Server belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Next Devtools MCP for developer tools work and Yeelight Metadata MCP Server 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.
Next Devtools MCP is listed as free. Auth: no auth required. Yeelight Metadata MCP Server has no declared pricing — check the project's own site. 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 vercel-next-devtools-mcp and yeelight-metadata-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Next Devtools MCP has a quality signal of 86/100 (Excellent) with 8 views, 0 installs and 828 GitHub stars. Yeelight Metadata MCP Server has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
