nomos MCP Bridge
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_TLS_REJECT_UNAUTHORIZED | No | Set to '0' to allow self-signed certificates from nomos controllers. | 0 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_controllersA | Lists all registered nomos controllers with their names, URLs, and which one is currently active. |
| select_controllerA | Connects to a nomos controller by name. Disconnects from any previously connected controller. After connecting, all tools, resources, and prompts from that controller become available. |
| add_controllerA | Registers a new nomos controller. If this is the first controller, it is automatically selected. |
| remove_controllerA | Removes a registered controller by name. If it is the currently connected controller, the connection is closed. |
| open_setupA | Opens the nomos MCP Bridge setup page in the default browser, where controllers can be added via a web form. |
| connection_statusA | Shows the current connection status — which controller is connected and whether the connection is active. |
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 6 tools
Each tool has a distinct purpose: adding, removing, selecting, listing controllers, checking connection status, and opening setup. No two tools overlap in functionality.
Most tools follow a clear verb_noun pattern (e.g., add_controller, list_controllers), but 'connection_status' is a noun_noun form, slightly deviating from the pattern.
With 6 tools, the server is well-scoped for managing controller registrations and connections, covering essential operations without unnecessary bloat.
The tool set covers core CRUD for controllers (add, remove, list, select) plus connection status and setup. A minor gap is the lack of an explicit disconnect tool, though select_controller handles it implicitly.