CAST Imaging MCP Server 3.1 (beta)

Starting release 3.1.0-beta4, 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. See Architecture for how the components fit together.

This is a substantial change to the installation and configuration of the component. The installation instructions are therefore documented separately from the current functional release:

  • 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

See the installation and configuration instructions below.

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.

See Architecture.
Microsoft Windows

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

See Installation on Microsoft Windows.
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.

See Installation on Linux via Docker.
Meta Tool mode

The meta-tool architecture allows an AI aware client to work with CAST Imaging through a small set of general-purpose tools rather than loading (around 50) individual tools in advance. In 3.1 the tool surface profile is set per MCP server.

See Meta Tool mode.
FAQ

Answers to a series of security and data safety related frequently asked questions about CAST Imaging’s MCP (Model Context Protocol) server.

See Frequently Asked Questions.

Not yet documented for 3.1

The following installation options are documented for the current functional release only. They are based on the Docker installation media and have not yet been revised for the MCP Aggregator Gateway architecture introduced in 3.1.0-beta4:

Do not follow those pages against a 3.1.0-beta4 or later installation media: the configuration file, the mounted paths and the published port have all changed.