nmos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NMOS_USE_HTTPS | No | Whether to use HTTPS for API requests. | false |
| NMOS_VERIFY_TLS | No | Whether to verify TLS certificates. | true |
| NMOS_AUTH_ENABLED | No | Enable IS-10 OAuth2 authentication. | false |
| NMOS_REGISTRY_URL | No | URL of the NMOS Registry. Leave unset to auto-discover via mDNS. | |
| NMOS_QUERY_VERSION | No | Query API version to use. | v1.3 |
| NMOS_AUTH_CLIENT_ID | No | OAuth2 client ID. | |
| NMOS_AUTH_TOKEN_URL | No | OAuth2 token endpoint URL. | |
| NMOS_AUTH_CLIENT_SECRET | No | OAuth2 client secret. | |
| NMOS_CONNECTION_VERSION | No | Connection API version to use. | v1.1 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| registry_infoA | Show the resolved NMOS registry (config or mDNS), reachability and resource counts. |
| list_nodesA | List NMOS Nodes in the registry. Optionally filter by label substring. |
| list_devicesC | List NMOS Devices (a Node hosts one or more Devices). |
| list_sendersB | List Senders (media egress points) advertised in the registry. |
| list_receiversC | List Receivers (media ingest points) advertised in the registry. |
| list_flowsC | List Flows (the essence a Sender transmits). |
| list_sourcesC | List Sources (the abstract origin of one or more Flows). |
| get_resourceB | Get one resource by id. |
| query_resourcesA | Query a resource collection with an IS-04 filter. Pass |
| get_senderB | Show a Sender's IS-05 staged + active connection state and its constraints. |
| get_receiverC | Show a Receiver's IS-05 staged + active connection state and its constraints. |
| get_sender_transport_fileA | Fetch a Sender's SDP transport file (the description a Receiver needs to subscribe). |
| connect_sender_to_receiverA | Connect a Sender to a Receiver (route media) with an immediate IS-05 activation. Pulls the Sender's SDP transport file and stages it on the Receiver with master_enable=true, then activates immediately. Returns the Receiver's resulting active state. |
| disconnect_receiverA | Disconnect a Receiver (clear its subscription and disable it) with immediate activation. |
| enable_senderB | Enable a Sender (master_enable=true) so it transmits, with immediate activation. |
| disable_senderB | Disable a Sender (master_enable=false) so it stops transmitting, with immediate activation. |
| bulk_connectA | Connect several Sender->Receiver pairs at once.
|
| stage_receiverC | Advanced: send a raw IS-05 staged PATCH body to a Receiver (full control of transport_params/activation). |
| stage_senderB | Advanced: send a raw IS-05 staged PATCH body to a Sender (e.g. set multicast destination). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/leif-cipriani/nmos-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server