> 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/http-mcp-server-configuration.md). # HTTP MCP Server Configuration The following section describes the steps required to configure the IZ HTTP MCP server in various IDEs. {% hint style="info" %} * Every request must carry two headers: **`x-falcon-service-url`** with the URL of your IZ Suite instance and **`x-falcon-access-token`** with a token generated as described in [Generating MCP Token](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/generating-mcp-token.md). * In a multi-tenant installation the value of **`x-falcon-service-url`** must be your **tenant's** URL (for example `https://acme.izsuite.example.com`). The tenant is identified from this URL; a request for an unknown or suspended tenant is rejected, and a token from another tenant is not accepted. * The tools offered are those of your tenant: the common IZ tools plus the automation tasks of your tenant that are marked **`Include in MCP Server`** {% endhint %} ### Visual Studio Code * Open the preferences and search for MCP * Click on **`MCP: Add Server`** -> **`HTTP (HTTP or Server-side Events)`** * Enter the URL (Eg: http(s)://\/mcp and click enter) and name as **`iz-suite-mcp-server`** * A mcp.json file with the entered details will be opened * Add the following headers **`x-falcon-service-url`**, **`x-falcon-access-token`** * To generate a token, refer token generation * The final configuration should look something like ```json "iz-suite-mcp-server": { "url": "http(s):///mcp", "type": "http", "headers": { "x-falcon-service-url": "http(s)://", "x-falcon-access-token": "" } } ``` ### Cursor IDE * Open the preferences and search for MCP * Click on **`View: Open MCP Settings`** * In the settings screen click on **`New MCP Server`** and add the below configuration: ```json "iz-suite-mcp-server": { "url": "http(s):///mcp", "type": "http", "headers": { "x-falcon-service-url": "http(s)://", "x-falcon-access-token": "" } } ``` * To generate a token, refer token generation * Save the mcp.json file. * Navigate back to Cursor Settings tab and toggle the enable switch.
### Copying the Configuration from IZ Suite The ready-to-use configuration for your instance, including the correct headers and hostname, can be copied from **`Global Settings`** -> **`MCP Server Setup`**. Replace the token placeholder with your generated token. #### Troubleshooting | Response | Cause | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | `401` / authentication error | The token is missing, expired, or was generated in a different tenant than the service URL. | | `404 Unknown or inactive tenant` | The **`x-falcon-service-url`** does not match a tenant hostname, or the tenant is suspended. | | Tool list is empty or misses a task | The token's role lacks the permission required by the tool, or the automation task is not marked **`Include in MCP Server`**. | ### See Also * [Enabling MCP Server](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/mcp-server-installation.md) * [Generating MCP Token](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/generating-mcp-token.md) * [Configuring STDIO MCP Server](/product-guides/integral-zone/iz-suite/iz-core/mcp-server/stdio-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/http-mcp-server-configuration.md?ask=&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.