Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

CAST Imaging MCP Server

by CAST-Extendversion 3.0.4i★ –iRuns on your computer
Registry nameio.github.CAST-Extend/imaging-mcp-server

Install

Overview

Description from the maker (original English)

MCP server exposing CAST Imaging software architecture insights to AI agents

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: Streamable HTTP
  • Category: Other
  • You need to fill in: HOST_CONTROL_PANEL, SERVICE_HOST

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: HOST_CONTROL_PANEL, PORT_CONTROL_PANEL, SERVICE_HOST, MCP_SERVER_PORT

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "imaging": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HOST_CONTROL_PANEL",
        "-e",
        "PORT_CONTROL_PANEL",
        "-e",
        "SERVICE_HOST",
        "-e",
        "MCP_SERVER_PORT",
        "docker.io/castimaging/imaging-mcp-server:3.0.4"
      ],
      "env": {
        "HOST_CONTROL_PANEL": "your-value",
        "PORT_CONTROL_PANEL": "your-value",
        "SERVICE_HOST": "your-value",
        "MCP_SERVER_PORT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add imaging --env HOST_CONTROL_PANEL=your-value --env PORT_CONTROL_PANEL=your-value --env SERVICE_HOST=your-value --env MCP_SERVER_PORT=your-value -- docker run -i --rm -e HOST_CONTROL_PANEL -e PORT_CONTROL_PANEL -e SERVICE_HOST -e MCP_SERVER_PORT docker.io/castimaging/imaging-mcp-server:3.0.4

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "imaging": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HOST_CONTROL_PANEL",
        "-e",
        "PORT_CONTROL_PANEL",
        "-e",
        "SERVICE_HOST",
        "-e",
        "MCP_SERVER_PORT",
        "docker.io/castimaging/imaging-mcp-server:3.0.4"
      ],
      "env": {
        "HOST_CONTROL_PANEL": "your-value",
        "PORT_CONTROL_PANEL": "your-value",
        "SERVICE_HOST": "your-value",
        "MCP_SERVER_PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "imaging": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HOST_CONTROL_PANEL",
        "-e",
        "PORT_CONTROL_PANEL",
        "-e",
        "SERVICE_HOST",
        "-e",
        "MCP_SERVER_PORT",
        "docker.io/castimaging/imaging-mcp-server:3.0.4"
      ],
      "env": {
        "HOST_CONTROL_PANEL": "your-value",
        "PORT_CONTROL_PANEL": "your-value",
        "SERVICE_HOST": "your-value",
        "MCP_SERVER_PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • HOST_CONTROL_PANEL required env
    CAST Imaging Control Panel hostname or IP
  • PORT_CONTROL_PANEL env
    CAST Imaging Control Panel port
  • SERVICE_HOST required env
    Hostname or IP of the machine running the MCP server
  • MCP_SERVER_PORT env
    Internal port the MCP server container listens on

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account CAST-Extend, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32606 servers in this category
  • Published to the registry more recently than 16% of the other 32606 servers in this category
  • Basic checks equal to or better than 100% of the other 32606 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is CAST Imaging MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: HOST_CONTROL_PANEL, SERVICE_HOST

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (3.0.4) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Georgia MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Georgia MCP

by abgeo

An MCP server for Georgian public data, read from the organizations that publish it.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

CAST Imaging MCP Server

Overview

The CAST Imaging MCP Server bridges the gap between AI agents and real software architecture by exposing comprehensive software intelligence through the Model Context Protocol (MCP). It allows the user to get insights about their applications ,transactions, dependencies, quality patterns, and architectural structures by prompting AI agents.

This service provides AI Agents with the understanding of your applications from portfolio-level inventories to granular object relationships. Whether you're exploring database schemas, analyzing transaction flows, investigating quality issues, the MCP server delivers precise, paginated data that enables informed architectural decisions.

Use Cases
  • Portfolio-level exploration: List applications available in your CAST Imaging and provides detailed information about them.
  • Application architecture analysis: Explore architectural graphs at different levels and visualize system structure.
  • Transaction & data flow mapping: Analyze transactions, trace data entity interaction networks, explore complex objects and sequencing.
  • Quality & security insights: Identify vulnerabilities, cloud readiness blockers and structural flaws in the applications.
  • Database schema exploration: Browse database tables, columns, relationships, and constraints across applications.
  • Object-level investigation: Search objects and their properties and analyze caller/callee relationships.

Table of Contents

  • Prerequisites
  • Quick Start
  • Installation
  • Configuration Reference
  • Running (HTTP)
  • Windows Installation
  • VS Code + GitHub Copilot Setup
  • Verification & Test Queries
  • Toolsets & Tools
  • Troubleshooting
  • Security Notes
  • Package Contents
  • Support

Prerequisites

Required
  • Linux system with Docker installed and running.
  • CAST Imaging‑APIs service reachable from this host
  • MCP‑aware client (e.g., GitHub Copilot in VS Code, Claude Desktop)
  • CAST Imaging API Key (generate from your Imaging user profile)
Download
  • Download the installer for CAST Imaging MCP server

The MCP server should run on a Linux system. CAST Imaging‑APIs may run on the same or a different Linux machine.


Quick Start

  1. Verify Imaging‑APIs is live:
   curl -H "x-api-key: <your-imaging-api-key>"         http://{CONTROL_PANEL_HOST}:8090/imaging/apis/rest/ready

expected: true

2. **Extract** the installer zip.
  1. Configure config/app.config and .env.
  2. Start the server with ./run.sh --install.
  3. Configure client (VS Code Copilot or Claude) with your server URL.
  4. Test queries (see examples below).

Installation of CAST Imaging MCP server

1) Extract the installer
com.castsoftware.imaging.mcpserver.docker.1.0.2-funcrel/

├─ config/ │ └─ app.config ├─ .env # hidden; use ls -a ├─ docker-compose.yml ├─ run.sh ├─ README.md └─ copilot-instructions.md

2) Verify CAST Imaging‑APIs

Make sure the Control Panel/registry is reachable and Imaging‑APIs is ready (see Quick Start step #1).

3) Configure server

Edit config/app.config:

HOST_CONTROL_PANEL="your-control-panel-host"   # REQUIRED: Control Panel service registry host/IP

PORT_CONTROL_PANEL=8098 # Default Control Panel registry port IMAGING_PAGE_SIZE=1000 # Internal fetch batch size IMAGING_DISPLAY_PAGE_SIZE=20 # Page size in responses IMAGING_CODE=False # Source code access via MCP (security sensitive) DEBUG_MODE=false # Debug mode to see the activity in logs IMAGING_DOMAIN="default" # Imaging domain/tenant CONTROL_PANEL_SSL_ENABLED=false # Set true only if Control Panel config/eureka is on HTTPS MCP_TOOL_SURFACE_PROFILE="full" # MCP tool exposure profile: "intents" or "full" MCP_INTENTS_HIDDEN_FUNCTIONS="" # Comma-separated structural functions hidden from intents mode SERVICE_HOST="your-service-host" # REQUIRED: The IP/hostname of the machine on which the MCP Server is running SSL_CA_BUNDLE="" # Optional PEM bundle for private/self-signed CAs

Set your exposed port in .env (hidden file):

MCP_SERVER_PORT=8282

Tip: On Linux, files starting with a dot (like .env) are hidden. Use ls -a to view.

4) Start
chmod +x run.sh

./run.sh --install

This launches the Docker Compose stack and the MCP server.

If you use SSL_CA_BUNDLE, place the PEM file in a certificates/ folder next to docker-compose.yml. The compose file mounts that folder into the container at /app/certificates.


Configuration Reference

HOST_CONTROL_PANEL (Required)

Default: None (user needs to provide the value) Description: IP or hostname of the machine running the Control Panel Service.

This is a service registry used by Imaging to register and discover its internal services. It is automatically deployed when you install Imaging. You should enter the IP address of the Linux machine running the Imaging Control Panel service.

PORT_CONTROL_PANEL

Default: 8098 Description: Control Panel registry port.

IMAGING_PAGE_SIZE

Default: 1000 Description: Sets the number of records the MCP server fetches per request (internal batching). Tune for throughput.

IMAGING_DISPLAY_PAGE_SIZE

Default: 20 Description: Sets how many records are shown per page in the user-facing response. Tune for UX.

IMAGING_CODE

Default: False Description: Controls whether the agent can access source code via the MCP server.

It's false by default, as agents typically work on open repos. Enabling it can expose source code to anyone with MCP access, making it a potential security risk, especially relevant for clients like Claude desktop without direct repo access.

DEBUG_MODE

Default: false Description: Debug mode will show teh activity in the logs. When set to true it will show the tool picked, the API called and the result for each user prompt. When set to false, it will only show the tool picked and the corresponding API called.

IMAGING_DOMAIN

Default: default Description: Imaging domain/tenant used to fetch data in multi-tenant environments.

CONTROL_PANEL_SSL_ENABLED

Default: false Description: Set to true when Control Panel config/eureka endpoints run on HTTPS.

MCP_TOOL_SURFACE_PROFILE

Default: full Description: Selects the MCP tool exposure profile. Use full to expose the complete toolset, or intents for the meta-tool surface.

MCP_INTENTS_HIDDEN_FUNCTIONS

Default: empty Description: Comma-separated list of structural functions to hide when MCP_TOOL_SURFACE_PROFILE is set to intents.

SERVICE_HOST (Required)

Default: None (user needs to provide the value) Description: IP/hostname of the machine on which the MCP Server is running.

SSL_CA_BUNDLE

Default: empty Description: Optional path to a PEM CA bundle for private/self-signed certificate chains. With the Docker installer, place the PEM under ./certificates/ and reference it as /app/certificates/ .pem.


Running (HTTP)

Start the server with:

chmod +x run.sh

./run.sh --install


Windows Installation

This section provides detailed steps for installing and configuring the CAST Imaging MCP Server on Windows systems.

Prerequisites for Windows
  • Windows system
  • CAST Imaging‑APIs service running and accessible
  • MCP‑aware client (e.g., GitHub Copilot in VS Code, Claude Desktop)
  • CAST Imaging API Key (generate from your Imaging user profile)
1) Download and Extract
  1. Download the installer package for windows.
  2. Extract the zip file to your preferred location
  3. Navigate to the extracted directory

Package contents:

com.castsoftware.imaging.mcpserver.__MCP_VERSION__*/

├─ mcpserver/ ├─ tools/ ├─ configuration.conf ├─ mcp-server-installer.bat └─ README.md

2) Verify CAST Imaging‑APIs

Make sure the Control Panel/registry is reachable and Imaging‑APIs is ready:

curl -H "x-api-key: <your-imaging-api-key>" 

http://{HOSTNAME_CONTROL_PANEL}:8090/rest/ready

expected: true

3) Configure Server

Edit configuration.conf with your environment settings:

HOSTNAME_CONTROL_PANEL="your-control-panel-host"      # Required: IP or hostname of Control Panel server

SERVICE_HOST="your-service-host" # Required: IP/hostname of the MCP Server machine PORT_CONTROL_PANEL=8098 # Default Control Panel registry port MCP_SERVER_PORT=8282 # Default MCP server port INSTALL_DIR=C:\Program Files\Cast\Imaging-MCP-Server # Default installation location CONFIG_DIR=C:\ProgramData\CAST\Imaging-MCP-Server # Default config files location IMAGING_PAGE_SIZE=1000 # Records per internal request IMAGING_DISPLAY_PAGE_SIZE=20 # Records per response page IMAGING_CODE=False # Enable source code access (security consideration) DEBUG_MODE=false # Debug mode to see the activity in logs IMAGING_DOMAIN=default # Imaging domain/tenant CONTROL_PANEL_SSL_ENABLED=false # Set true only if Control Panel config/eureka is on HTTPS MCP_TOOL_SURFACE_PROFILE=full # MCP tool exposure profile: full or intents MCP_INTENTS_HIDDEN_FUNCTIONS= # Comma-separated structural functions hidden from intents mode SSL_CA_BUNDLE= # Optional PEM bundle for private/self-signed CAs

4) Install as Windows Service

Run the installation using the batch script:

mcp-server-installer.bat --install configuration.conf

This installs the MCP server as a Windows service. After successful installation, you'll see a Windows service named "CAST Imaging MCP Server" in your services list.

5) Verify Installation

Check that the service is running:

  • Open Services (services.msc)
  • Look for "CAST Imaging MCP Server"
  • Ensure status is "Running"
Windows-Specific Operations
Update MCP Server

To update an existing installation:

mcp-server-installer.bat --update

No configuration changes needed for updates.

Uninstall MCP Server

To completely remove the MCP server:

mcp-server-installer.bat --uninstall

This removes the Windows service and cleans up all MCP-related files.

Get Help

For available commands:

mcp-server-installer.bat --help

Available commands:

mcp-server-installer.bat --install configuration.conf   : Install CAST Imaging MCP server

mcp-server-installer.bat --update : Update CAST Imaging MCP server mcp-server-installer.bat --uninstall : Uninstall CAST Imaging MCP server mcp-server-installer.bat --help : Display help message

Windows Troubleshooting
IssuePossible CauseSolution
Service won't startConfiguration errorCheck %CONFIG_DIR%/setup-config/app.config
Connection refusedService not runningRestart "CAST Imaging MCP Server" service
Installation failsInsufficient permissionsRun installer as Administrator

VS Code + GitHub C

Only the beginning is shown; read the rest in the repo

Ask PopNx