Mia-Platform Console

The Mia-Platform Console MCP Server enables seamless integration with Mia-Platform Console APIs through the Model Context Protocol, allowing you to automate interactions and manage MCP-enabled workflows with your preferred tools and clients.

How to use

You can connect to the Mia-Platform Console MCP Server from MCP clients such as code editors or CLI tools that support MCP authentication and discovery. The server supports both remote HTTP access and a local, stdio-based runtime. To begin, configure your client with either the HTTP endpoint or the local Node-based server you run on your machine. The server will handle authentication and provide the necessary MCP endpoints to discover tools, prompts, and other capabilities exposed by Mia-Platform Console.

How to install

Prerequisites You must have access to a Mia-Platform Console instance and a host address for that instance. You also need Node.js installed if you plan to run the local MCP server. It is recommended to install dependencies and build the project before starting the MCP server.

Step 1: Install dependencies and build the project if you are running locally.

npm ci
npm run build

Step 2: Create an environment configuration file. Copy the default environment file to a local .env file and adjust values as needed.

cp default.env .env

Step 3: Start the MCP server locally using the runtime command shown in the example. This runs the server in stdio mode.

{
  "mcp": {
    "servers": {
      "mia-platform-console": {
        "command": "node",
        "args": [
          "${workspaceFolder}/mcp-server",
          "start",
          "--stdio",
          "--host=https://console.cloud.mia-platform.eu"
        ]
      }
    }
  }
}

Alternatively, you can start the service after the build by running the following command in your terminal and then connect your client to the provided URL.

node mcp-server start

If you plan to connect via an HTTP endpoint from your MCP client, you can point your client to the HTTP URL shown in the example configuration.

Additional sections

Environment variables load automatically from a .env file if present in the project root. You can customize the values as needed to control logging, server port, host, and authentication behavior.

Environment variables

Environment variables located inside a file named .env are automatically included at service startup.

LOG_LEVEL=info
PORT=3000
CONSOLE_HOST=
MIA_PLATFORM_CLIENT_ID=
MIA_PLATFORM_CLIENT_SECRET=
CLIENT_EXPIRY_DURATION=300