Visit Azul.com Support

Connecting an MCP Client

Table of Contents
Need help?
Schedule a consultation with an Azul performance expert.
Contact Us

Azul Intelligence On-Premises serves the Model Context Protocol (MCP) at /api/public/v1/mcp. An assistant or agent that supports MCP can read your inventory through it. The endpoint uses the same API tokens and the same limits as the Integration API.

Settings > MCP in the web interface shows the commands on this page with the address of your own installation filled in.

The Endpoint

 
https://<host>:<port>/api/public/v1/mcp

MCP runs on the application port. When a reverse proxy sits in front of your installation, it only has to pass /api/public/v1/mcp.

Authenticate with an API token as a bearer credential in the Authorization header. See API Tokens for how to mint one.

A request that carries a browser Origin header is refused, unless LJVMI_PUBLIC_API_MCP_ALLOWED_ORIGINS lists that origin. Assistants that run outside a browser send no Origin header and need no setting.

The Tools

The endpoint offers multiple tools. All of them are read-only, so an assistant can look at your inventory but cannot change it.

Claude Code

 
claude mcp add --transport http --scope user <name> '<endpoint>' --header 'Authorization: Bearer <token>'

Codex

Put the token in an environment variable, and pass the name of that variable:

 
codex mcp add <name> --url '<endpoint>' --bearer-token-env-var <VAR>

Limits

Tool calls, result sizes, and open sessions have limits. See MCP limits.