nomos MCP Bridge

A local MCP proxy that manages connections to one or more nomos system controllers. Instead of configuring each controller individually in your AI client, the bridge lets you register multiple controllers and switch between them via natural language.

Works with any MCP-compatible AI client — Claude Desktop, Cursor, Windsurf, ChatGPT Desktop, and more.

How It Works

MCP Client ──stdio──► nomos-mcp-bridge ──Streamable HTTP──► nomos Controller A
                      (local proxy)    ──Streamable HTTP──► nomos Controller B
                                       ──Streamable HTTP──► nomos Controller C

The bridge runs as a local MCP server (via stdio) and connects to nomos controllers over the network using the MCP Streamable HTTP transport. All tools, resources, and prompts from the connected controller are dynamically proxied — the bridge stays lightweight and always exposes exactly the capabilities the controller supports.

Prerequisites

• Node.js 18 or later
• A nomos system controller with MCP enabled (Skills > MCP) and a configured token
• Network access to the controller from your machine

MCP Client Configuration

The bridge works with any AI client that supports the Model Context Protocol. No manual installation needed — just add the config and your client will run the bridge automatically via npx.

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "nomos": {
      "command": "npx",
      "args": ["-y", "nomos-mcp-bridge"]
    }
  }
}

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "nomos": {
      "command": "npx",
      "args": ["-y", "nomos-mcp-bridge"]
    }
  }
}

Windsurf

Add to your Windsurf MCP config (~/.codeium/windsurf/mcp_config.json):

{
  "mcpServers": {
    "nomos": {
      "command": "npx",
      "args": ["-y", "nomos-mcp-bridge"]
    }
  }
}

Claude Code (CLI)

claude mcp add nomos -- npx -y nomos-mcp-bridge

Other MCP Clients

Any client supporting stdio-based MCP servers can use the bridge. The command is:

npx -y nomos-mcp-bridge

Adding Controllers

Option 1: Via the Setup Web Page

Tell your AI assistant to open the setup page:

"Open the nomos setup page"

This opens a local web UI in your browser where you can enter the controller name, URL, and MCP token.

Option 2: Via AI Chat

Tell your AI assistant to add a controller:

"Add my nomos controller 'Wohnhaus' at 192.168.1.100 with token abc123"

The assistant will use the add_controller tool to register it.

Option 3: Manually

Edit ~/.config/nomos-mcp/controllers.json:

{
  "controllers": [
    {
      "id": "some-uuid",
      "name": "Wohnhaus",
      "url": "https://192.168.1.100/mcp",
      "token": "your-mcp-token"
    }
  ],
  "activeControllerId": "some-uuid"
}

Usage

Once controllers are registered, simply tell your AI assistant which one to use:

"Connect to controller Wohnhaus"

"Switch to Büro controller"

"Show me all my controllers"

After connecting, all nomos tools are available as if the client were directly connected to the controller. You can:

• Control devices ("Turn off the living room lights")
• Create scenes and automations
• Check system status
• Configure the smart home

Bridge Tools

The bridge provides these management tools:

| Tool | Description | |------|-------------| | list_controllers | List all registered controllers | | select_controller | Connect to a controller by name | | add_controller | Register a new controller | | remove_controller | Remove a registered controller | | open_setup | Open the setup web page in the browser | | connection_status | Show current connection status |

Configuration

Controller credentials are stored in ~/.config/nomos-mcp/controllers.json. The setup web server runs on http://localhost:18900 (auto-increments if the port is in use).

Security Notes

• Tokens are stored in plain text in the config file. Ensure appropriate file permissions.
• The setup web server only listens on 127.0.0.1 (localhost) and is not accessible from the network.
• nomos controllers use HTTPS with self-signed certificates by default. Node.js may reject these — set NODE_TLS_REJECT_UNAUTHORIZED=0 in your MCP client config if needed:

{
  "mcpServers": {
    "nomos": {
      "command": "npx",
      "args": ["-y", "nomos-mcp-bridge"],
      "env": {
        "NODE_TLS_REJECT_UNAUTHORIZED": "0"
      }
    }
  }
}

Development

# Clone the repository
git clone https://github.com/nomos-system/nomos-mcp-bridge.git
cd nomos-mcp-bridge

# Install dependencies and build
npm install
npm run build

# Run
npm run start

# Or build and run in one step
npm run dev

License

MIT