Searches and reads the official Hungarian myIO smart-home controller documentation (manual, API reference, FAQ) with no sign-in.
What you can do
Get an overview of the docs: product line, hardware and legacy name mapping, version marks, sources
List the table of contents, filtered by source or title text
Keyword search across manual, API reference, FAQ and product data, returning section ids, URLs and snippets
Read the full Markdown text of a section by id, in parts for long sections
When to use it
Useful when answering questions about myIO smart-home controllers, their API, setup or FAQ, and when you need to check whether a documented feature is released, coming soon or in beta.
Requirements
Remote streamable HTTP endpoint at docs-mcp.myio.hu; no authentication, API keys or environment variables declared. Content is in Hungarian, so Hungarian keywords work best.
Before you install
Read-only documentation access; no data is written. The manual and API reference describe the latest development state, including unreleased and beta features, so availability must be checked against the product pages. The docs do not cover prices, delivery dates, vendor comparisons or undocumented compatibility.
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%2Fdocs/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.
Overview of the myIO documentation: what myIO is, the current product line and its availability, how hardware and older names in the docs map to product names (e.g. Due = myIO Server V3), what version marks such as [4.x] mean, and the list of sources.
Takes no parameters.
myio_toc
myIO table of contents
Table of contents of the myIO documentation: every section id with its title and size. Optional filters: source (manual, api, faq, products, site) and text contained in the section title.
Parametersfiltersource
myio_search
Search myIO docs
Keyword search in the myIO documentation (manual, API reference, FAQ, product data). The content is in Hungarian: Hungarian keywords match best, and matching ignores accents and Hungarian word endings. Returns section ids, URLs, version marks and a snippet; myio_read returns the full section.
Parameterslimitqueryrequiredsource
myio_read
Read myIO doc section
Full text (Markdown) of one section of the myIO documentation, by its id from myio_search or myio_toc. Long sections come in parts; the response names the next part.
Parametersidrequiredpart
Version history
1
v0.3.1LatestNov 20, 2026
Score
83%
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 listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
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.