---
title: MCP Server Configuration
slug: neurons/help/en_us/mcp-server-configuration
createdAt: 2026-11-17T05:56:50.919Z
---

Model Context Protocol (MCP) servers help to connect the AI agents, such as Claude and other MCP-capable clients, to Ivanti Neurons environment. AI agents can query live Ivanti Neurons data and provide real-time insights, automation, and reporting for your IT infrastructure.

MCP servers are organized by domain, with each server providing capabilities for specific functions, such as device inventory, patch compliance, vulnerability exposure, software distribution, and IT service management (ITSM).

Ivanti supports this solution with the following AI agent clients:

- GitHub Copilot CLI
- GitHub Copilot
- Claude

Before you begin, ensure that you have the following:

- An active Ivanti Neurons account with administrative access.
- A Client ID from an AI agent app registration. You can create or reuse an existing registration under **Admin&#x20;**> **App Registrations**.
- An AI agent client that supports OAuth-based MCP server connections.

To connect an AI agent to Ivanti Neurons, complete the following tasks:

1. Login to the Ivanti Neurons tenant as an administrator.
2. Navigate to **Admin** > **Settings > AI Settings&#x20;**&#x73;ection.
3. Toggle on the **Enable Ivanti MCP servers.**
4. Create an AI Agent app registration
   Navigate to **Admin > App Registrations > New Registration**.&#x20;
5. Select **AI Agent** and **Register**.&#x20;
6. On the **Complete this registration** screen, copy the Neurons Auth URL specific to MCP server and the client ID.
7. Select the MCP server domain that matches your requirements.
   Each domain is a self-contained set of tools for a specific area of IT operations.
8. Configure the MCP connection in your AI agent client by entering tenant URL and the client ID.&#x20;
9. Complete the authentication on your AI agent client.
   Recommended method: OAuth is recommended to connect an MCP-capable AI-agent to Ivanti Neurons.

:::hint{type="info"}
Copy the client ID and Auth URL to a secure location before you select **Finish** and close. You cannot view them again after closing the window. If you lose the values, you must create a new app registration.
:::

:::hint{type="info"}
On an AI agent client, the Neurons Auth URL, must be appended at the end with **/mcp/\<domain>/v1.**

For example `https://your-tenant.ivanticloud.com/mcp/devices/v1`
:::

## Supported MCP server domains

| Domain                          | Domain name             | Primary purpose                                                    | Key capabilities                                                                                                        |
| ------------------------------- | ----------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| Device discovery and management | `device`                | Query and analyze device inventory and health.                     | Device counts, OS and manufacturer breakdowns, device health, warranty status, DEX scores, and OData filtering.         |
| Natural-language data queries   | `dataservices`          | Convert natural-language questions into structured device queries. | Natural language to OData conversion, interpreted filters, and ready-to-run queries.                                    |
| Patch management                | `patch`                 | Monitor patch compliance, deployment status, and exploit risks.    | Patch deployment history, failure analysis, deployment trends, exploit severity, risk scores, and patch configurations. |
| Vulnerability exposures         | `exposures`             | Identify and analyze vulnerability exposures.                      | Exposure summaries, CVE details, severity information, and OData pagination.                                            |
| Software inventory              | `software-inventory`    | Track installed software and lifecycle status.                     | Software inventory, installation details, version tracking, manufacturer information, and end-of-life status.           |
| Software distribution           | `software-distribution` | Monitor software deployments and application configurations.       | Device and package deployment status, application catalog queries, and application configurations.                      |
| Reporting and analytics         | `reporting`             | Access report configurations and execution details.                | Report jobs, filtering, pagination, execution history, and distribution lists.                                          |
