> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/mcp-server/mcp-server-installation.md).

# MCP Server Installation

## Enabling IZ MCP Server

{% hint style="warning" %}

* MCP server feature requires IZ Suite version 1.4.0 or above
* From IZ Suite version 26.3.1 the MCP server starts automatically with the IZ Server. The steps below describe how to verify and restart it.
  {% endhint %}

#### MCP Server Endpoint <a href="#mcp-server-endpoint" id="mcp-server-endpoint"></a>

1. The HTTP MCP server is available at http(s)://\<YOUR\_HOST\_NAME>/mcp as soon as the IZ Server is running.
2. In a multi-tenant installation, use the tenant's hostname. The tenant is identified from the service URL sent by the MCP client; see [HTTP MCP Server Configuration](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/http-mcp-server-configuration.md).
3. To check the list of available tools check available tools section

#### Restarting MCP Server <a href="#restarting-mcp-server" id="restarting-mcp-server"></a>

1. Navigate to **`Global Settings`** -> **`MCP Server Setup`**
2. Click on **`Restart MCP Server`**. The action is available to administrators of the platform tenant (or of the instance, in a single-tenant installation).
3. The MCP server also restarts automatically when the **`MCP Server Settings`** global setting is saved.

#### Upgrading from 1.4.x <a href="#upgrading-from-14x" id="upgrading-from-14x"></a>

The **`MCPServerMonitorSchedule`** entry under **`Audit`** -> **`Scheduler Audit Logs`** and its **`Enable Schedule`** / **`Disable Schedule`** actions no longer exist. No action is required after upgrading; the MCP server starts with the server.

### Enabling / Starting MCP Server (only till 1.4.2 version)

1. Navigate to **`Audit`** -> **`Scheduler Audit Logs`**
2. Click on the **`Enable Schedule`** action item against **`MCPServerMonitorSchedule`** to start the MCP Sever.
3. Once the schedule is enabled, the HTTP MCP server can be accessed at http(s)://\<YOUR\_HOT\_NAME>/mcp
4. To check the list of available tools check available tools section

### Stopping MCP Server (only till 1.4.2 version)

1. Navigate to **`Audit`** -> **`Scheduler Audit Logs`**
2. Click on the **`Disable Schedule`** action item to stop the MCP Sever.

### See Also

* [Configuring STDIO MCP Server](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/stdio-mcp-server-configuration.md)
* [Configuring HTTP MCP Server](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/http-mcp-server-configuration.md)
* [MCP Tools](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/mcp-tools.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/mcp-server/mcp-server-installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.