Mockd vs Tolpo
A side-by-side look at the Mockd and Tolpo 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 Mockd for home automation work over a hosted endpoint; choose Tolpo 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?
Choose Mockd when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
TChoose Tolpo when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tolpo | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 56/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 149 | 8 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Mockd | View Tolpo |
Tools & capabilities
Mockd tools
No tool names declared yet. Check the project README from the listing page.
Tolpo 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.
Mockd
{
"mcpServers": {
"getmockd-mockd": {
"url": "https://api.example.com/users"
}
}
}
Tolpo
{
"mcpServers": {
"tolpo": {
"command": "npx",
"args": [
"-y",
"tolpo"
]
}
}
}
Frequently asked questions
Mockd is categorized under Home Automation and uses a remote HTTP/SSE transport. Tolpo belongs to Home Automation and uses a local stdio subprocess. Pick Mockd for home automation work and Tolpo 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.
Mockd is listed as free. Auth: no auth required. Tolpo 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 getmockd-mockd and tolpo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mockd has a quality signal of 56/100 (Good) with 2 views, 0 installs and 149 GitHub stars. Tolpo has 44/100 (Fair) with 0 views, 0 installs and 8 GitHub stars.