.prompts vs Yeelight Metadata MCP Server
A side-by-side look at the .prompts 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.
.
.promptsDeveloper Tools.prompts, the home to all your AI prompts, everywhere you need them.25EmergingAuth: not declaredY
Yeelight Metadata MCP ServerDeveloper Tools · Remote HTTP/SSEYeelight home metadata and guarded management workflows.36FairAuth: not declaredVerdict: choose .prompts for developer tools work; 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?
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 | . .prompts | Y Yeelight Metadata MCP Server |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 25/100 · Emerging | 36/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | 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 | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View .prompts | View Yeelight Metadata MCP Server |
Tools & capabilities
.prompts 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.
.prompts
No confirmed install command for .prompts yet — follow the setup steps linked from its listing page rather than a guessed package name.
Yeelight Metadata MCP Server
{
"mcpServers": {
"yeelight-metadata-mcp-server": {
"url": "https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp"
}
}
}
Frequently asked questions
.prompts is categorized under Developer Tools and uses an install path we have not confirmed yet. Yeelight Metadata MCP Server belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick .prompts 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. .prompts has no confirmed install command yet — follow its own setup instructions.
.prompts has no declared pricing — check the project's own site. 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 prompts and yeelight-metadata-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, .prompts has a quality signal of 25/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Yeelight Metadata MCP Server has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
