# indigo-mcp-server
## 基本信息
- Slug: `mlamoure-indigo-mcp-server`
- Source: modelscope
- Publisher: @mlamoure/indigo-mcp-server
- Categories: home-automation-and-iot / rag-systems
- Hosted: No
- License: Unknown
- Source URL: https://www.modelscope.cn/mcp/servers/@mlamoure/indigo-mcp-server
## 简介
暂无描述。
## 安装提示

```bash
**Setup:** 1. Configure Indigo Reflector in Web Server Settings 2. Use your Reflector API key 3. Replace `your-reflector-url.indigodomo.net` with your actual Reflector URL 4. Replace `YOUR_REFLECTOR_API_KEY` with your Reflector API key #### Scenario 2: HTTPS on LAN with Self-Signed Certificate ```json { "mcpServers": { "indigo": { "command": "npx", "args": [ "-y", "mcp-remote", "https://your-local-hostname-or-ip:8176/message/com.vtmikel.mcp_server/mcp/", "--header", "Authorization:Bearer YOUR_LOCAL_SECRET_KEY" ], "env": { "NODE_TLS_REJECT_UNAUTHORIZED": "0" } } } }
```

## MCP Server 详情

# Indigo MCP Server Plugin

A Model Context Protocol (MCP) server plugin that enables AI assistants like Claude to interact with your Indigo home
automation system through natural language queries.

## What It Does

Search, analyze, and control your Indigo devices using natural language:

- "Find all light switches in the bedroom"
- "Show me temperature sensors"
- "Turn on the garage lights"
- "What devices are currently on?"
- "Execute the bedtime scene"

## Server Requirements

- **Indigo Domotics**: 2024.2 or later
- **macOS**: 10.15 (Catalina) or later
- **CPU**: Intel Mac (2013+) or Apple Silicon (M1/M2/M3/M4)
    - Note: LanceDB (used for vector search) requires AVX2 CPU instructions
    - Most Intel Macs from 2013 onwards support AVX2
    - All Apple Silicon Macs are fully supported
- **OpenAI API Key**: Required for semantic search ([Get API key](https://platform.openai.com/api-keys))
    - Sends device metadata to OpenAI for embeddings (minimal cost)
    - Only device names, types, descriptions sent - no sensitive data

## Installation

1. **Install Node.js**: If not already installed, install Node.js for `npx` command
   - Via Homebrew: `brew install node`
   - Or download from [nodejs.org](https://nodejs.org/)
   - Verify installation: `npx --version`
2. **Install Plugin**: Add MCP Server plugin to Indigo via Plugin Manager
3. **Configure Plugin**: Enter OpenAI API key in plugin preferences
4. **Create MCP Server Device**: Add new "MCP Server" device in Indigo
5. **Wait for Indexing**: Plugin will index your Indigo database (takes time on first run)
6. **Configure Claude Desktop**: Add configuration to `claude_desktop_config.json`

## Optional Features

- **InfluxDB Connection information**: Required for historical data analysis queries
- **LangSmith**: Optional debugging and tracing of AI prompts. Not needed for most people.

### MCP Server Device Setup

The MCP Server Indigo device is what creates the actual MCP Server.

- **Server Access**: Configured via MCP Server device in Indigo
- **Single Server**: Plugin enforces one MCP Server device per installation

### Authentication & Security

 **IMPORTANT**: All MCP connections require authentication using an Indigo API key as a Bearer token.

**How to obtain API keys:**

- **Local/LAN access**: Create a `secrets.json` file
  with [local secrets](https://wiki.indigodomo.com/doku.php?id=indigo_2024.2_documentation:indigo_web_server#local_secrets)
    - Location: `/Library/Application Support/Perceptive Automation/Indigo [VERSION]/Preferences/secrets.json`
    - See documentation link above for JSON format details
    - Note: Restart Indigo Web Server after creating/modifying this file
- **Remote access**: Use your Indigo Reflector API key from your Reflector settings

### Claude Desktop / MCP Client Configuration

Requirements:
- **Node.js**: Required for MCP client connection ([Download](https://nodejs.org/))
    - Provides `npx` command used by Claude Desktop configuration
    - Install via Homebrew: `brew install node`
    - Or download from [nodejs.org](https://nodejs.org/)

For Claude Desktop -- Add one of the following configurations to
`~/Library/Application Support/Claude/claude_desktop_config.json` based on your use case:

In all cases, you will need an API Key. For this, you have two choices:

- **Indigo Reflector API Key**: Obtained from your Reflector settings
- **Local Secret**: Created in `secrets.json` file (
  see [documentation](https://wiki.indigodomo.com/doku.php?id=indigo_2024.2_documentation:indigo_web_server#local_secrets))

#### Scenario 1: HTTPS via Reflector (Most Common, Enables remote access outside your home)

**Use when:**

- Accessing Indigo from outside your local network
- Security: Encrypted connection with valid SSL certificate

```json
{
  "mcpServers": {
    "indigo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://your-reflector-url.indigodomo.net/message/com.vtmikel.mcp_server/mcp/",
        "--header",
        "Authorization:Bearer YOUR_REFLECTOR_API_KEY"
      ]
    }
  }
}
```

**Setup:**

1. Configure Indigo Reflector in Web Server Settings
2. Use your Reflector API key
3. Replace `your-reflector-url.indigodomo.net` with your actual Reflector URL
4. Replace `YOUR_REFLECTOR_API_KEY` with your Reflector API key

#### Scenario 2: HTTPS on LAN with Self-Signed Certificate

```json
{
  "mcpServers": {
    "indigo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://your-local-hostname-or-ip:8176/message/com.vtmikel.mcp_server/mcp/",
        "--header",
        "Authorization:Bearer YOUR_LOCAL_SECRET_KEY"
      ],
      "env": {
        "NODE_TLS_REJECT_UNAUTHORIZED": "0"
      }
    }
  }
}
```

**Setup:**

1. Create a local secret (
   see [local secrets documentation](https://wiki.indigodomo.com/doku.php?id=indigo_2024.2_documentation:indigo_web_server#local_secrets))
    - Create/edit: `/Library/Application Support/Perceptive Automation/Indigo [VERSION]/Preferences/secrets.json`
    - Restart Indigo Web Server after modifying
2. Replace `your-local-hostname-or-ip` with your Indigo server IP/hostname
3. Replace `YOUR_LOCAL_SECRET_KEY` with your generated local secret
4. `NODE_TLS_REJECT_UNAUTHORIZED=0` disables certificate validation (required for self-signed certs)
5. Replace port 8176 if you are not using the default Indigo Web Server port

#### Scenario 3: HTTP on Local/LAN

If you have HTTPS disabled on your Indigo Web Server.

```json
{
  "mcpServers": {
    "indigo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://your-local-hostname-or-ip:8176/message/com.vtmikel.mcp_server/mcp/",
        "--allow-http",
        "--header",
        "Authorization:Bearer YOUR_LOCAL_SECRET_KEY"
      ]
    }
  }
}
```

**Setup:**

1. Create a local secret (
   see [local secrets documentation](https://wiki.indigodomo.com/doku.php?id=indigo_2024.2_documentation:indigo…