SandBase CLI vs Yeelight Metadata MCP Server
A side-by-side look at the SandBase CLI 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 SandBase CLI for aggregators work over a hosted endpoint; 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 SandBase CLI when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You want tools like
sandbase_discover, sandbase_inspect, sandbase_run.
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 | Aggregators | Developer Tools |
| Quality signal | 61/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | other | 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 | 186 | 0 |
| Directory activity | 11 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View SandBase CLI | View Yeelight Metadata MCP Server |
Tools & capabilities
SandBase CLI tools 7
sandbase_discoverSearch all 2,000+ available AI models and APIs — freesandbase_inspectGet input schema, current price, and a ready-to-run template — freesandbase_runExecute a model or API endpoint — free for data APIs, paid for modelssandbase_run_getPoll status/result of an async run (video gen, etc.) — freesandbase_runsList your recent runs with their cost — freesandbase_accountCheck account balance — freesandbase_run_cancelCancel an Agent Service run — free
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.
SandBase CLI
{
"mcpServers": {
"sandbase-cli": {
"url": "https://tensorblock.co/mcp/servers/github-sandbaseai-cli-c4e113db"
}
}
}
Yeelight Metadata MCP Server
{
"mcpServers": {
"yeelight-metadata-mcp-server": {
"url": "https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp"
}
}
}
Frequently asked questions
SandBase CLI is categorized under Aggregators and uses a remote HTTP/SSE transport. Yeelight Metadata MCP Server belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick SandBase CLI for aggregators 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.
SandBase CLI is listed as free. Auth: other. 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 sandbase-cli and yeelight-metadata-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SandBase CLI has a quality signal of 61/100 (Good) with 11 views, 0 installs and 186 GitHub stars. Yeelight Metadata MCP Server has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
