Nature Remo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCESS_TOKEN | Yes | Your Nature Remo access token from https://home.nature.global/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesB | List devices on the home |
| list_appliancesA | List appliances on the home |
| operate_tvD | Operate a TV appliance |
| operate_airconD | Operate an aircon appliance |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools 'list_appliances' and 'list_devices' have overlapping purposes, as both list things on the home without clear distinction. This could cause confusion for an agent selecting which tool to use.
All tool names follow a consistent 'verb_noun' pattern using snake_case (e.g., 'list_appliances', 'operate_aircon'), making them predictable and easy to understand.
With 4 tools, the set is appropriately scoped for a simple home automation server, covering basic listing and operation tasks without being overwhelming.
The tool set covers listing and operating two specific appliances, but lacks operations for other common actions like turning off, scheduling, or managing devices/appliances, leaving notable gaps.