nature-remo
MCP Server for the Nature Remo API.
claude mcp add --transport stdio noboru-i-nature-remo-mcp-server npx -y noboru-i/nature-remo-mcp-server \ --env ACCESS_TOKEN="<YOUR_TOKEN>"
How to use
This MCP server acts as a bridge to the Nature Remo API, exposing a set of typed tools that let you discover and control Nature Remo devices from your MCP-enabled automation environment. The server provides utilities to list your devices and appliances, and to operate common appliances like TVs and air conditioners by sending commands through the Nature Remo API. Use the available tools to fetch device inventories and perform actions with minimal required parameters (and optional parameters where supported) to tailor automation flows to your setup.
To begin, configure the server with your Nature Remo access token, then run it via your preferred launcher (for example, using npx as shown in the examples). Once the server is running, you can call tools such as list_devices or list_appliances to retrieve current device lists, or operate_tv and operate_aircon to perform actions on specific devices by providing the necessary identifiers and command details.
How to install
Prerequisites:
- Node.js (recommended: v14 or newer) and npm installed on your system
- Access token from Nature Remo (to be provided as an environment variable)
Installation steps:
- Ensure you have Node.js and npm installed
- Install the MCP server package (via npx or install locally):
# Run directly with npx (no local install required)
npx -y noboru-i/nature-remo-mcp-server
# Or install locally (optional)
npm install -D noboru-i/nature-remo-mcp-server
- Provide your Nature Remo access token via environment variable ACCESS_TOKEN:
export ACCESS_TOKEN=<YOUR_TOKEN>
- Start the MCP server (example using npx):
npx -y noboru-i/nature-remo-mcp-server
If you install locally, you can start with a script in package.json, for example:
"scripts": {
"start": "node path/to/server.js" // or the appropriate entry point
}
Then run:
npm run start
Additional notes
Environment variables and configuration tips:
- ACCESS_TOKEN is required to access the Nature Remo API; ensure it is kept secure and never committed to version control.
- If you rotate your token on Nature Remo, update the ACCESS_TOKEN value accordingly.
- The server exposes tools for listing devices/appliances and for operating specific appliances; if a tool returns an error, verify that the applianceId and any required parameters are correct and that the token has the necessary permissions.
- For operating actions (operate_tv, operate_aircon), you can include optional parameters to refine the command (e.g., times, temperature, direction).
- When using VS Code or Claude Desktop configurations, ensure the environment variable is set in the mcp.json or mcpServers configuration to avoid authentication failures.
Related MCP Servers
context7
Context7 MCP Server -- Up-to-date code documentation for LLMs and AI code editors
obsidian -tools
Add Obsidian integrations like semantic search and custom Templater prompts to Claude or any MCP client.
MiniMax -JS
Official MiniMax Model Context Protocol (MCP) JavaScript implementation that provides seamless integration with MiniMax's powerful AI capabilities including image generation, video generation, text-to-speech, and voice cloning APIs.
mcp-bundler
Is the MCP configuration too complicated? You can easily share your own simplified setup!
akyn-sdk
Turn any data source into an MCP server in 5 minutes. Build AI-agents-ready knowledge bases.
promptboard
The Shared Whiteboard for Your AI Agents via MCP. Paste screenshots, mark them up, and share with AI.