# Nomid MDM

> Nomid MDM is a freemium MCP server for developer tools. Query and command an Android and VR device fleet through scoped assistant access. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Pricing:** Freemium
- **Platforms:** Web, API, Android
- **Website:** https://www.nomidmdm.com/en/developers/mcp
- **MCP Registry name:** com.nomidmdm/nomid-mdm
- **Categories:** developer tools, cloud and infrastructure
- **Listing updated:** 2026-11-14

## About

Nomid's server turns fleet questions into chat: how many devices use a policy, which have not synced since a date, why a device cannot be reached remotely, is out of sync or fails to enroll, and where a given app is installed. It can also read the company's own plan, link to a portal page and look up Nomid's public plans and list prices.

Write access is opt-in and split into scopes. `mcp:read` covers the read tools, `mcp:devices:command` allows commands such as lock and reboot, `mcp:provisioning` creates enrollment QR codes, and `mcp:policies:write` allows policy change proposals. Wipe and other destructive commands sit behind a separate `mcp:devices:destructive` scope, take one device per call, and need the company to enable destructive commands in its AI agent access settings.

Assistants connect through Sign in with Nomid (OAuth) or an API key sent as a bearer token or X-API-Key header. A connection made for one company sees only that company, while All companies I manage lets `list_companies` and a company argument reach each one. The server is stateless streamable HTTP, and the docs recommend a dedicated read-only key as the starting point.

## Features

- **Fleet questions:** Ask about device counts per policy, stale syncs and where an app is installed.
- **Fault diagnosis:** Investigate devices that are unreachable, out of sync or failing to enroll.
- **Device commands:** Send commands such as lock, reboot or policy change with an extra permission.
- **Provisioning QR codes:** Create enrollment QR codes for new devices.
- **Scoped OAuth consent:** Users untick scopes on the consent page and the company can switch AI access off.
- **Multi-company access:** Connections can span every company a user manages.

## Good for

- Find which devices have not synced since a given date
- Work out why a kiosk tablet will not enroll
- Lock or reboot several devices from a chat
- Generate a provisioning QR code for a new Android device
- Check how many devices use a given policy

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http nomid-mdm https://mcp.nomid.tech/emm/api/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://mcp.nomid.tech/emm/api/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "nomid-mdm": {
      "url": "https://mcp.nomid.tech/emm/api/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

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

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "nomid-mdm": {
      "serverUrl": "https://mcp.nomid.tech/emm/api/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

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

## Tools

- `get_company_plan`: The company's own Nomid plan (FREE, PRO or ENTERPRISE), its term and billing cadence, its device limit (the Free plan's; paid plans have none), how many devices count as billable now and which devices count, and whether anything blocks new enrollments. The device limit never blocks enrollment: devices above it still enroll and count. Use it before any claim about this company's plan, limit or bill
- `list_companies`: List the companies this connection can work in, each with its `company` value, tenant and device counts (total, by status, and ACTIVE devices with no check-in for 7 days or more), plus totals across every listed company. Use it to answer questions about the whole fleet across companies, or to find a company, then pass its `company` value as the company argument of any other tool to work in it. A c
- `send_device_command`: Send one command to real, physical devices, the command chosen with command: one device (assetId, its pathName from search_devices or get_device), several (assetIds, up to 50 pathNames) or every device of a policy that can take commands (devicesInPolicy, its pathName from list_policies; at most 50). For several devices make one call with all of them, never one call per device. It runs immediately:
- `send_destructive_command`: Send one command that cannot be undone to one real, physical device, the command chosen with command; these are never sent to several devices at once. It runs immediately, with no approval step in Nomid: before calling it, tell the user exactly what it does to which device and get an explicit yes, and never resend one after an unconfirmed result without asking. assetId is the device's pathName fro
- `count_devices`: Count the authenticated company's devices, optionally narrowed by device status, assigned policy (or several, with "policies"), "lastSyncBefore" (each device's last sync, the portal's "Last sync", before an instant: use it for devices not synced, not seen or offline since a date), "lastSeenBefore" (asset record updated before an instant; not proof of being offline) and/or "missing" (devices withou
- `diagnose`: Diagnose a problem in one call, the problem chosen with area. Run it before guessing a cause. For enrollment, inspect current saved defaults and recent QR options, including offline and mobile-data flags, before attributing a failure to Wi-Fi. Saved QR options do not identify the QR scanned or prove live Google state. remote_access, policy_sync (one device, by assetId): Diagnose a problem area on 
- `get_device`: Get full details for a single device (asset) in the authenticated company by its path name, including policy assignment, custom data, tags, hardware specifications and last known location. Its "lastSync" is the portal's "Last sync" (last contact); "syncedAt" is only the last status report. managedDevice.policyVersion is the current version of the device's policy, the number the portal and policy r
- `get_fleet_summary`: Get a compact aggregate summary of the authenticated company's fleet: total device count, a breakdown by status, and the security-posture summary (secure/at-risk/compromised/unknown counts, encryption/ADB/unknown-sources/dev-settings counts, and up to 10 risky device path names). Never returns a full device list - use search_devices for that.
- `list_device_apps`: Get the apps actually on one device (asset) in the authenticated company, from the app report the device last sent: package name, app name, version, state (INSTALLED, or REMOVED when it was uninstalled), installedBy (POLICY, USER, SYSTEM = came with the device) and source. Use it to answer "is app X installed / which version", to check whether a policy app reached the device, and to find the packa
- `list_device_commands`: Get the most recent commands sent to a device (asset) in the authenticated company, newest first: type, status, timestamps, a short outcome code and who sent it. requestedByType USER means a portal user, named in requestedBy by email (also when Nomid Agent sent it for them; SUPPORT is Nomid or partner support); API_KEY means an integration, named by the key's name. No requestedBy means no person o
- `list_device_user_logins`: Get who logged in on the company's devices: the sessions of device users, newest first. Each has the device user (name, auth PIN, SSO or EXTERNAL = authenticated by the customer's own system, and that system's externalUserId), the asset (assetId, serial number, name), loginAt, logoutAt, expiresAt, open, and who reported the login and the logout: DEVICE (the Nomid agent on the device), API (the cus
- `read_device_document`: Nomid staff only (Nomid system admins; refused for everyone else). Reads one device's stored documents as they are in the database, every field included: asset (with asset.managedDevice, the device as last reported: appsReport with each app's keyedAppStates, events, hardware, network, memory and power events, non-compliance) and currentStatus (the agent's reports: nomidApps, checkups, appMetadata,
- `search_devices`: Search the authenticated company's device fleet. Devices are returned as "assets" - the business-level representation of an enrolled or tracked device, including its policy assignment, custom data, tags, hardware specifications and last known location. Results are paginated; use "page" and "size" to page through a large fleet. Optionally narrow the search by device status, assigned policy, "lastSy
- `search_nomid_site`: Search Nomid's public website (www.nomidmdm.com) for plans and pricing: the Free, Pro and Enterprise plans and their device limits, list prices per Android and VR device per month in USD, EUR and BRL, the annual discount, what each plan includes (e.g. remote access and the API are paid), and the pricing FAQ (payment methods, plan changes, pilots, custom plans). Returns excerpts with their page URL
- `search_library`: Search the company's Nomid Library: its apps (private Android apps uploaded to Nomid, with package name, version and categories) or, with kind "links", its web links (VR library). Returns how many the Library has, how many match and the matches, each app with its portal link. Only the Library: an app from Google Play or one a policy installs is not here (read the policy with get_policy_settings), 
- `get_portal_link`: Get the URL of a device, policy or library app in the Nomid portal, to show the user where to see or manage it, or of a fixed portal page (kind "page": the dashboard, the devices or policies list, the library, enrollment, a company settings tab such as users, billing or ai_agents, an integration such as android_enterprise or sso). Needs the id of the object (the "pathName" of an asset or policy, a
- `apply_policy_proposal`: Apply a policy change you proposed (propose_policy_change, create_policy, rollback_policy) by its proposalId. Only call this after showing the user the proposal's change list and getting their explicit approval in this conversation. A HIGH impact proposal can't be applied here: a person approves it in the Nomid portal, so give the user its approvalUrl, and get_policy_proposal then shows the outcom
- `propose_policy_change`: Propose one change to an existing policy: pass policyId and exactly one of the parts below; for changes of several kinds, call it once per part. Parts: settings (the restrictions, security, connectivity, location, reporting and Play Store settings get_policy_settings lists); apps (add, remove or change how apps are installed); homeScreen (kiosk mode, the Nomid launcher or the device's own home scr
- `create_policy`: Propose creating a new policy, optionally with setting changes. With fromPolicyId it is a copy (duplicate) of that policy - its apps, settings and restrictions. Without it, it is a new policy from scratch with Nomid's defaults (the Nomid Settings agent, device reporting, Play Protect enforced, the standard Android home screen, no other apps), in the default group. When the user asks for a new poli
- `find_app`: Find where an app is, by package name or by name, in one call: whether it is in a policy (its source - Google Play, the Nomid Store Library, a secure web app - its install type and whether it is the kiosk app), in the company's Library, on Google Play (by package name only) and installed on a device (from its last app report). Pass policyId, assetId or both; with assetId alone the device's own pol
- `get_policy_document`: Get a policy's full configuration as JSON, or the part at a path: Wi-Fi networks (openNetworkConfigurations), passwords, restrictions, system updates, the launcher, time and geo fences, app configurations and everything else. Secrets read as {"redacted": true}. Use it before propose_policy_change with edits, for anything get_policy_settings doesn't list. Without a path, apps are summarized: read /
- `get_policy_proposal`: Get a policy change proposal you made, by its proposalId: its change list, impact, status (PENDING, SUCCEEDED, FAILED, EXPIRED, ...), expiry and outcome. Once SUCCEEDED, result carries what applying it returned (for create_policy, the new policyId and version).
- `get_policy_revision_document`: Read a policy's saved historical configuration by revision ID from list_policy_revisions, with secrets replaced by {"redacted": true}. Returns the revision's policy version, providerVersion when recorded, save time and recorded audit actor. These describe saved configuration, never proof that a device applied it or that a person manually made the change. Read-only: creates no proposal and restores
- `get_policy_settings`: Get the settings of a policy that AI agents can change: for each one its id, label, group, current value, allowed values and whether changing it is high impact; plus the policy's version (the portal's number; every save raises it) and changedAt (when it was last saved), deviceCount and apps (package name, name, source, install type). Values: NOT_SET means left to the device or Google's default, CU
- `get_policy_usage`: Usage report of one policy (policyId) or of a whole policy group (policyGroup: every policy of it added up, one row per policy), over the last 7 or 30 complete days (UTC), for the devices on the policies now: screen time (foreground hours of apps), the most-used apps by screen time, data usage (Wi-Fi and mobile MB) and the apps that used the most data, with a daily series. The same numbers as the 
- `list_policies`: List every policy defined in the authenticated company, or with query those matching it, with overview information (path name, display name, description, version, policy group, deviceCount). deviceCount is the number of devices on the policy (0 when none), not counting deleted or reprovisioned ones. Configuration detail of each policy is excluded: read one policy's with get_policy_document or get_
- `list_policy_revisions`: List the saved revisions of a policy, newest first: revision number, when and by whom it was saved, and the policy version it produced. changedBy is recorded audit attribution, not proof of a manual human action. Read a saved configuration with get_policy_revision_document; saved versions do not prove a device applied them. Use rollback_policy only to propose a restore.
- `rollback_policy`: Propose rolling a policy back to one of its revisions (list_policy_revisions): its whole configuration - apps, settings, restrictions, networks - is restored, and its name goes back to the revision's when they differ (the change list shows it); description, tags and group stay. Nothing changes yet: this returns a proposal with the differences. Show it to the user and get their explicit approval. A
- `create_provisioning_qr_code`: Create a QR code that enrolls a new or factory-reset Android device into this company under the given policy. Each call creates a new enrollment token that stops working 24 hours later, so create one only when the user asks for a QR code to enroll devices, and never reuse an older one. The QR image is delivered to the user directly with this result: do not describe, transcribe or rebuild it. To us
- `read_company_chats`: Nomid staff only (Nomid system admins; refused for everyone else). Lists one company's portal AI chat conversations, reviewed or not, most recently active first (default: the last 7 days), each with its sessionId, title and dates. Use company to name the company; another customer's needs an "All Nomid customers" connection. Pass a sessionId to read that conversation (a long one comes in parts: pas
- `read_flagged_chats`: Nomid staff only (Nomid system admins; refused for everyone else). Lists the reviews of portal AI chat conversations, newest first (default: FLAGGED in the last 7 days), each with its company, severity, signals, failure categories, the reviewer's summary and humanOffer (the "Talk to a human" offer the chat showed the user: SHOWN, ACCEPTED, DISMISSED or null). Pass a reviewId to read that review's 

## FAQ

### How do I sign in?

Use Sign in with Nomid (OAuth) from claude.ai, ChatGPT or Claude Code, or send a Nomid API key as a bearer token or X-API-Key header.

### Can the assistant wipe devices?

Only with the destructive scope or key permission, and only when the company has turned on destructive commands. It is one device per call.

### Is there a free plan?

Yes. Free covers up to 10 devices with no time limit, excludes remote access and the API, and includes connecting AI agents.

### Which key permissions are needed for reading?

DEVICES_READ and POLICIES_READ are enough for every read tool.

### Is Nomid MDM free?

Nomid MDM has a free plan, with paid plans for more usage or features.

### How do I add Nomid MDM to Claude Code?

Run this command in your terminal: claude mcp add --transport http nomid-mdm https://mcp.nomid.tech/emm/api/mcp

### What are the best alternatives to Nomid MDM?

The closest alternatives to Nomid MDM are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.
- [Claude Code Ultimate Guide](https://ai-powered.com/mcp/claude-code-ultimate-guide): Claude Code Ultimate Guide is an open-source MCP server for ai models and llm tooling.
- [Concord MCP](https://ai-powered.com/mcp/concord-mcp): Concord MCP is a freemium MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/nomid-mdm
