Install the CAST Imaging MCP Server

Install the CAST Imaging MCP Server on Microsoft Windows or Linux via Docker, or install MCP Server 3.0.x

Overview

The CAST Imaging MCP Server is required to interface AI clients with CAST Imaging results via its API. Choose the installation that matches your environment. Once installed, developers configure their AI clients as described in Connect your AI client.

Starting release 3.1.0-funcrel, the installation media delivers an MCP Aggregator Gateway and three MCP servers behind it. Your MCP-aware client continues to connect to CAST Imaging, which redirects MCP requests to the MCP Aggregator Gateway; the gateway then routes each request to the MCP server able to answer it, presenting the tools of all enabled MCP servers - structural, semantic search and Text2Cypher - as a single tool surface. Compared with MCP Server 3.0.x:

  • the configuration file changes - a single .env file on Linux via Docker, replacing config/app.config
  • the port CAST Imaging redirects MCP requests to changes from 8282 to 8285
  • a Neo4j instance is required by the semantic search and Text2Cypher MCP servers
  • the tool surface profile is now set per MCP server

CAST Imaging compatibility

MCP Server release Required API version/CAST Imaging release
≥ 3.1.0-funcrel ≥ 3.6.9-funcrel

Installation options

Microsoft Windows

This option is specifically for a direct installation on your Microsoft Windows machine.

Linux via Docker

/ This option is specifically for a direct install on Docker running on a Linux operating system. All components are provided as Docker images.

Architecture

How the MCP Aggregator Gateway aggregates the structural, semantic search and Text2Cypher MCP servers behind a single endpoint: components, tool surface, ports, HTTP endpoints and security posture.

MCP Server 3.0.x

Installation instructions for MCP Server 3.0.x and earlier. Installation on Linux via Podman and in an air-gapped environment is documented for 3.0.x only and has not yet been revised for 3.1.0.