Developers

MCP Reference

Connect your MCP client to Opsole’s MCP server and use provided tools to retrieve device and migration data.

Integration

Opsole exposes an MCP server you can connect to from compatible MCP clients. Configure your client to point at the Opsole MCP endpoint and authenticate with your API key if required.

// Example MCP client config (pseudo)
{
  "mcpServers": {
    "opsole": {
      "transport": "sse", // or "stdio" depending on your client
      "url": "https://api.opsole.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Note: Transport and URL may vary by environment. Refer to your MCP client’s documentation for supported transports.

Available Tools

Core tools exposed by the Opsole MCP server.

get-device-details

READ

Fetch device metadata and current migration status.

get-intune-device-list

READ

List devices as reported by Microsoft Intune.

migrated-device-list

READ

List devices that have completed migration.

get-migrated-device-details

READ

Retrieve details for a specific migrated device.

Example Tool Call

Typical JSON-RPC request/response structure used by MCP clients when invoking tools.

// Request
{
  "jsonrpc": "2.0",
  "id": "1",
  "method": "tools/call",
  "params": {
    "name": "get-device-details",
    "arguments": { "deviceId": "abc-123" }
  }
}
// Response
{
  "jsonrpc": "2.0",
  "id": "1",
  "result": {
    "content": {
      "deviceId": "abc-123",
      "model": "Surface Pro 9",
      "status": "migrating",
      "lastSeen": "2025-01-10T09:41:00Z"
    }
  }
}

Exact fields depend on your Opsole configuration and environment.

More Documentation

See the full docs for client libraries, schemas, and advanced integration guides.