---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# MID-less log ingestion for HLA

# MID-less log ingestion for HLA from an MCP Client {#ariaid-title1}

Release version: Australia  
Updated August 18, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Set up MID-less log ingestion integrations for Health Log Analytics (HLA) directly from an AI-enabled MCP Client, without opening the ServiceNow UI.

## Using an MCP Client to set up a MID-less integration {#itom-mcp-server-hla-ingest__overview}

If the HLA app is installed on your ServiceNow instance, the ITOM
MCP Server Console lets you set up HLA integrations for MID-less log data ingestion. You can set up integrations from any AI-enabled MCP Client. You can use an MCP Client, such as AWS Claude, to create the integrations entirely through natural-language prompts, without navigating to the Integrations Launchpad.  
The HLA ingest tools associated with the ITOM MCP Server Console enable you to perform the following tasks from the MCP Client:

* Find existing MID-less ingest integrations by name.
* Create an ingest integration or rename an existing one. The MCP Client returns the integration ID, HTTP endpoint, gRPC endpoint, and access token for a newly created integration.
* Turn an integration on or off. An integration must be deactivated before it can be renamed.
* Generate a new access token for an integration. The previous token remains valid until its original expiration.
{#itom-mcp-server-hla-ingest__ul_odv_qp3_hkc}

## Workflow {#itom-mcp-server-hla-ingest__workflow}

MID-less ingestion integration setup is part of the ITOM MCP Server Console workflow:

1. An administrator opens their MCP Client application and describes the integration they need.

   For example: "Create an OTel ingestion integration named otel-prod."  
   Note:  
   By default, integrations are created in an inactive state. However, the MCP tools are capable of creating an active integration. For example, tell the MCP Client: "Create an active OTel ingestion integration named otel-prod."
2. The MCP Client sends the request to the ITOM MCP Server Console using the Model Context Protocol (MCP).
3. The ITOM MCP Server Console authenticates the user against ServiceNow role-based access control.
4. The ITOM MCP Server Console creates or updates the ingest integration record in HLA.
5. The ITOM MCP Server Console returns the integration details, including endpoint and token information, to the MCP Client.
{#itom-mcp-server-hla-ingest__ol_hla_ingest_workflow}
**Related concepts**   

* [Use the ITOM
  MCP Server Console to perform ITOM tasks](https://www.servicenow.com/docs/DaYRmyZyj6avCkpX8KedrQ "Connect an AI-enabled MCP Client application to your ServiceNow environment using the ITOM MCP Server Console. Use the MCP Client to investigate alerts, review configuration item (CI) reliability, assess incident impact, and create service level objectives (SLOs).")
* [MID-less log streaming for HLA](https://www.servicenow.com/docs/Dy3xpF7022XHtmW7IiCVIg "Health Log Analytics (HLA) can receive log data from external sources directly through the ITOM Gateway, without routing data through a MID Server. This architecture supports cloud-native log sources such as Amazon Data Firehose, Cribl, and OpenTelemetry, and is required for high-volume HLA deployments.")  
**Related tasks**   

* [Set up MID-less log ingestion using an MCP Client](https://www.servicenow.com/docs/sdCQCialiDTv3kutRgaZoQ "Create, configure, and activate MID-less log ingestion integrations for Health Log Analytics from an MCP Client.")