Froglet vs Yeelight Metadata MCP Server
A side-by-side look at the Froglet 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 Froglet 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 Froglet when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
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 | 45/100 · Fair | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | 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 | Community listing | Community listing |
| GitHub stars | 8 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Froglet | View Yeelight Metadata MCP Server |
Tools & capabilities
Froglet tools
No tool names declared yet. Check the project README from the listing page.
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.
Froglet
{
"mcpServers": {
"froglet": {
"command": "npx",
"args": [
"-y",
"froglet-mcp"
]
}
}
}
Yeelight Metadata MCP Server
{
"mcpServers": {
"yeelight-metadata-mcp-server": {
"url": "https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp"
}
}
}
Frequently asked questions
Froglet 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 Froglet 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.
Froglet is listed as free. 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 froglet and yeelight-metadata-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Froglet has a quality signal of 45/100 (Fair) with 3 views, 0 installs and 8 GitHub stars. Yeelight Metadata MCP Server has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
