Tolpo vs Govee
A side-by-side look at the Tolpo and Govee MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TolpoHome Automation · Local subprocess (stdio)Local-first control of TP-Link Tapo smart-home devices for AI agents44FairAuth: not declaredVerdict: choose Tolpo for home automation work as a local process; choose Govee for home automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
TChoose Tolpo when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
Choose Govee when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_scenes.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tolpo | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 44/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Tolpo | View Govee |
Tools & capabilities
Tolpo tools
No tool names declared yet. Check the project README from the listing page.
Govee tools 1
list_scenes
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.
Tolpo
{
"mcpServers": {
"tolpo": {
"command": "npx",
"args": [
"-y",
"tolpo"
]
}
}
}
Govee
{
"mcpServers": {
"govee": {
"command": "uvx",
"args": [
"govee-mcp"
]
}
}
}
Frequently asked questions
Tolpo is categorized under Home Automation and uses a local stdio subprocess. Govee belongs to Home Automation and uses a local stdio subprocess. Pick Tolpo for home automation work and Govee for home automation.
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.
Tolpo has no declared pricing — check the project's own site. Govee 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 tolpo and govee as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tolpo has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 8 GitHub stars. Govee has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.