mocop
Browse · Docs · Guide · Analyze

nomid-mdm

MCP server by Nomid · mcp

Nomid MDM: a company's Android and VR device fleet, its policies and enrollment. The API key or Sign in with Nomid connection decides the company. A connection that reaches several companies lists them with list_companies, and every other tool takes an optional company argument. How to work: find a device with search_devices (query = name, serial number, IMEI or tag), then get_device; answer fleet questions with count_devices (groupBy) or get_fleet_summary instead of paging through devices; when something does not work, call diagnose before guessing a cause; give the user the portalUrl links results carry. send_device_command acts on real, physical devices right away: confirm intent with the user first, and never resend a command after an unconfirmed result without asking. For several devices make one call with assetIds (up to 50) or devicesInPolicy, never one call per device. send_destructive_command (wipe, screen lock reset or change, relinquish ownership, uninstall apps, clear app…

Endpoint: https://api.nomid.tech/emm/api/mcp

Verification: observed. Source: crawl.

Capabilities (35)

  • get_attention_items
  • get_company_plan
  • list_companies
  • send_device_command
  • send_destructive_command
  • count_devices
  • diagnose
  • get_device
  • get_fleet_summary
  • list_device_apps
  • list_device_commands
  • list_device_user_logins
  • read_device_document
  • search_devices
  • search_nomid_site
  • search_library
  • get_portal_link
  • apply_policy_proposal
  • propose_policy_change
  • create_policy
  • explain_changes
  • find_app
  • find_policy_setting
  • get_policy_document
  • get_policy_proposal
About · Contact · Privacy