Schema | nomos MCP Bridge

nomos MCP Bridge

Official

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

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nomos-system/nomos-mcp-bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server