How to configure CAST Imaging on Cloud MCP Server

Overview

CAST Imaging on Cloud provides a Model Context Protocol (MCP) server that allows you to leverage your analysis results with AI clients like Claude Desktop, GitHub Copilot, and other MCP-compatible tools. The instructions below explain how to configure Github Copilot and quickly obtain results.

Prerequisites

An active CAST Imaging on Cloud subscription
Your personal API key (obtain from your CAST Imaging on Cloud dashboard):

Setup instructions for GitHub Copilot for Visual Studio Code

Refer to https://code.visualstudio.com/docs/copilot/customization/mcp-servers for more information.

Step 1 - Initial configuration

Install the GitHub Copilot extension (see https://marketplace.visualstudio.com/items?itemName=GitHub.copilot ) in Visual Studio Code.
Ensure you are signed in to GitHub and clone the repository you need to work with.
Create an mcp.json configuration file and place it in the .vscode/ folder for your Visual Studio Code workspace. The mcp.json must use the following template:

{
  "inputs": [
    {
      "id": "imaging-key",
      "type": "promptString",
      "description": "CAST Imaging on Cloud API Key"
    }
  ],
  "servers": {
    "CASTImaging": {
      "type": "http",
      "url": "https://castimaging.io/imaging/mcp/",
      "headers": {
        "x-api-key": "${input:imaging-key}"
      }
    }
  }
}

Step 2 - Verify the connection

When the mcp.json file is configured, you can verify the connection:

Launch Github Copilot
Enter your CAST Imaging API key when prompted
Run a test query, for example:

“List all of the apps available”

If configured correctly, your assistant should be able to access your CAST Imaging on Cloud account and respond with your project information, listing all the applications that are available to you.

Example prompts

Here are some example prompts to try:

“List 10 transactions in the application my_app”
“List some insights in application my_app”
“List some objects in application my_app”

Security best practices

Never share your API key with others or commit it to version control
Rotate your API keys regularly through the CAST Imaging on Cloud dashboard
Revoke unused keys to minimize security risks
Use separate keys for different applications or team members

Troubleshooting

Connection failure

Verify your API key is correct and active
Ensure your network allows connections to CAST Imaging on Cloud
Review your client’s logs for specific error messages

Slow response times

Check your internet connection
Verify the CAST Imaging on Cloud service status
Consider the size of datasets you’re querying