Nomid MDM

com.nomidmdmPublished by nomidmdm.comv1.0.0Updated Nov 7, 2026

Manage Android and VR device fleets: policies, kiosk mode, device commands and enrollment QR codes.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for Nomid MDM that lets an assistant manage Android and VR device fleets: policies, kiosk mode, device commands and enrollment QR codes.

What you can do
  • Manage device fleets and their enrollment, including generating enrollment QR codes
  • Apply and adjust device policies and kiosk mode settings
  • Send commands to managed Android and VR devices
  • Work through a hosted Nomid MDM endpoint rather than a local package
When to use it
Useful when you administer a Nomid-managed fleet of Android or VR devices and want an assistant to look up or change policies, kiosk configuration, device commands or enrollment steps without switching to the Nomid console.
Requirements
A remote streamable HTTP endpoint at api.nomid.tech. Authentication is required: either a Nomid API key sent as a bearer token in the Authorization header, or an OAuth 2.1 sign-in with Nomid when the header is omitted. A Nomid account with managed devices is implied.
Before you install
The server can change device configuration: policies, kiosk mode, device commands and enrollment codes affect real hardware in the field. The Authorization header carries a Nomid API key, so treat it as a secret and prefer the OAuth sign-in where possible. Device and policy data is handled by the third-party Nomid service.

Installation

In SourceWeft

  1. Open Nomid MDM in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.nomidmdm%2Fnomid-mdm/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nomid-mdm": {
      "type": "http",
      "url": "https://api.nomid.tech/emm/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.