
Home Automation Mcp
io.github.varvararattaPublished by GitHub account varvararattav1.0.0Updated Oct 24, 2026
MCP server for Home Automation
Overview
A hosted remote MCP endpoint for home automation, connected over streamable HTTP with no declared authentication.
- What you can do
- The listing gives no tool list, so the exact actions are not documented. It is presented as an MCP server for home automation, reachable as a hosted endpoint at a fixed address. The provider's README describes a farm of hosted MCP servers with zero-auth public APIs and paid tools billed through x402 (USDC on Base), with a free health check and discovery tools. Beyond that, the available material does not specify which devices, platforms or commands the server exposes.
- When to use it
- Consider it if you want to try connecting an assistant to a hosted home automation endpoint without installing anything locally. Because the tool set is undocumented, check what it actually exposes before relying on it for real device control.
- Requirements
- A remote MCP client that can connect to a streamable HTTP endpoint; no local runtime, package, environment variables or headers are declared. The README states that paid tools need an x402-capable MCP client, while health check and discovery tools are free.
Installation
In SourceWeft
- Open Home Automation Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.varvararatta%2Fhome_automation_mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"home-automation": {
"type": "http",
"url": "https://home-automation-mcp.mcpize.run/mcp"
}
}
}README
BotFactory MCP Farm
Hosted MCP servers on MCPize — zero-auth public APIs, freemium x402 (USDC on Base).
Catalog
See CATALOG.md for the full list with gateway URLs.
Connect
Requires an x402-capable MCP client for paid tools. health_check and discovery tools are free.
Awesome list entries
See AWESOME_ENTRIES.md.
Source: README.md at commit 14e36b4
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.