myIO Documentation
Server Details
Search and read the official myIO smart home documentation: manual, API reference, FAQ. No sign-in.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool has a distinct role: myio_about gives meta/orientation info, myio_toc enumerates sections, myio_search does keyword lookup, and myio_read returns full section text. The only near-neighbours (toc vs. search) are clearly separated as browsing-by-structure versus lookup-by-term, and each description explicitly points to the other for the next step.
All four tools use the same myio_ prefix followed by a single short lowercase identifier (about, read, search, toc). The pattern is predictable and uniform, so an agent can guess tool names reliably.
Four tools is a tight, well-scoped surface for a read-only documentation server: orient, browse, search, fetch. No tool looks redundant, and nothing obvious is missing that would require another endpoint.
The retrieval lifecycle is essentially covered: discovery via toc/search, paging handled by the part mechanism in myio_read, and orientation via myio_about. Minor gaps remain — sections can only be fetched by id, not by the URLs returned from search, and there is no way to retrieve multiple sections or the whole document at once.
Available Tools
4 toolsmyio_aboutmyIO overviewARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
myio_readRead myIO doc sectionARead-onlyIdempotentInspect
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.
Inputs: id (required), part.
myio_searchSearch myIO docsARead-onlyIdempotentInspect
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.
Inputs: query (required), limit, source.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Search and read the official MintMCP documentation, the enterprise MCP gateway.
Search and read official API, MCP, SDK, authentication and travel-power integration guides.
Search and read SYMONE documentation: service, prices, public API, MCP servers, sandbox, limits.
Search and read Lynta's public documentation.
Related MCP Servers
- AlicenseAqualityCmaintenanceProvides access to microCMS documentation, enabling AI assistants to search and retrieve the latest document content.43240 npm8MIT
- FlicenseNot gradedqualityDmaintenanceEnables searching and fetching documentation pages from a wide range of programming languages, frameworks, game engines, and tools. Supports multiple sources and returns relevant documentation snippets.1-
- AlicenseAqualityDmaintenanceProvides access to Agno framework documentation for AI agents, enabling search and retrieval of SDK references, API endpoints, code examples, and integration guides through MCP-compatible tools.73MIT

notifly-mcp-serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents to search Notifly documentation and SDK code examples for seamless integration.100 npm1-
Glama MCP Gateway
Add one secure layer between your agents and this server.