myIO Smart Home

hu.myioPublished by myio.huOfficial publisherv0.1.0Updated Nov 20, 2026

Check and control your myIO smart home from anywhere via the myIO Cloud. Needs a V4 controller.

The publisher's own server: myIO Documentation

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant check and control a myIO smart home through the myIO Cloud from anywhere.

What you can do
  • Check and control myIO smart home devices through the myIO Cloud.
  • Work from any location rather than only on the local network.
  • No tool list is published, so the exact set of actions an assistant can take is not documented here.
When to use it
Useful if you already run a myIO smart home with a V4 controller and want an assistant to query or adjust it remotely.
Requirements
A remote endpoint at mcp.myio.hu reached over streamable HTTP, with OAuth sign-in required. A myIO smart home with a V4 controller.
Before you install
OAuth grants the assistant access to your smart home account, so review the permissions requested. Because the server can control devices, actions may change the state of your home; the available tools are not documented, so verify what it can do before relying on it.

Installation

In SourceWeft

  1. Open myIO Smart Home in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/hu.myio%2Fsmart-home/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "myio-smart-home": {
      "type": "http",
      "url": "https://mcp.myio.hu/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestNov 20, 2026

Score

83% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Myio integrations