Loading your account…

Account

Plan free  Upgrade →
Status active
0 of 3 devices enrolled

License Key

Use this key during agent installation when prompted.

—
Download installer:

MCP Server

Connect your AI assistant to your enrolled device fleet. Use OAuth to sign in with your ML-EPM portal account and approve read-only access to your devices. API-key connections are also supported. Select your client:

In Claude Desktop or Claude.ai, open Connectors and add a custom remote connector named ML-EPM with this server URL:

  1. Choose OAuth / Sign in now when prompted.
  2. Choose Use Claude’s published identity (CIMD). Register automatically also works. Leave manual client ID, client secret, and request headers empty.
  3. Connect and sign in with your ML-EPM portal email and password in the browser window.
  4. Review the ML-EPM consent page and choose Allow access, then return to Claude.

If an older connection fails, remove it and add it again to clear its obsolete registration. The previous shared OAuth credentials no longer apply.

Claude connector setup guide

In ChatGPT on the web, open Plugins, choose + → Add custom MCP server, and name it ML-EPM. Use this server URL:

  1. Select OAuth and CIMD when offered; automatic registration (DCR) also works. Leave manual client ID and secret empty.
  2. Review the prompts and create the plugin. Complete browser sign-in with your ML-EPM portal account and approve Allow access.
  3. Install the plugin, then select it with @ in a conversation.

Availability depends on your workspace permissions. For a desktop app’s local MCP server settings, use the .

Official ChatGPT setup guide

In the desktop app or Codex IDE extension, open MCP servers in settings, add ML-EPM using Streamable HTTP, and enter this URL:

Save and restart the connection, then select Authenticate. Sign in with your portal account and approve consent. Leave API-key headers and manual OAuth credentials empty.

With the Codex CLI installed, add the server and authenticate from a terminal:

Or merge this entry into ~/.codex/config.toml, then run the login command above. Local clients on the same Codex host share this configuration:

Use /mcp to check the connection. When replacing an older setup, remove its API-key header and obsolete OAuth credentials before authenticating.

Official Codex MCP guide

API-key connection: Create .vscode/mcp.json in your workspace root (requires GitHub Copilot or Copilot Chat extension, VS Code 1.99+):

API-key connection: Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project root:

API-key connection: Add to ~/.codeium/windsurf/mcp_config.json:

Add an OAuth connection for your user account across projects:

Or add to .mcp.json in your project root (project-scoped, shareable with your team):

In Claude Code, run /mcp and authenticate ML-EPM. Sign in with your portal account and approve the consent page. Each team member signs in separately.

Merge this OAuth configuration into ~/.gemini/settings.json, preserving your other settings and servers:

Restart Gemini CLI and run the following at its interactive prompt:

Complete browser sign-in with your ML-EPM portal account and approve Allow access. Run /mcp list to check the connection and available tools. Use a local session with browser access for sign-in.

Validation status: Configuration follows Gemini CLI’s documentation. An end-to-end Gemini CLI connection to ML-EPM has not yet been verified.

Official Gemini CLI MCP guide

In an OAuth-capable MCP client, add this remote server URL and choose OAuth. The client discovers the sign-in settings automatically:

Sign in & approve: Use your ML-EPM portal email and password in the browser, review the requested access, and choose Allow access. The assistant can read only the devices in your account.

Use the client’s published identity (CIMD) or automatic registration (DCR), when offered. Leave manual client credentials and API-key headers empty for this flow. If your client requires a preconfigured OAuth client, contact ML-EPM support for a registration specific to that client.

Read permission telemetry:read
Stay connected offline_access (optional, when supported by your client)

Compatible clients refresh access automatically for up to 30 days after approval, then you sign in again. If a connection retains the old setup, remove it and add it again. The previous shared client ID and secret are obsolete.

API-key connection: Send an HTTP POST to the MCP endpoint from your HTTP client, SDK, or custom integration:

Your API key is for clients using an x-api-key header. OAuth connections do not need it. Keep keys private; regenerating this key affects API-key connections only.

API Key (optional):
—

MCP calls this period: 0 / —

Enrolled Devices

MachineAgent VersionEnrolledStatusUpgrade PolicyUpdate
Loading…