console

The Mia-Platform Console MCP Server exposes MCP-compliant endpoints that integrate with the Mia-Platform Console APIs. It enables automation and tool integration for developers and external tooling that rely on MCP discovery, tool prompts, and command execution against a Mia-Platform Console instance. After starting the server, clients can connect via the MCP interface and discover available tools, prompts, and actions exposed by the Console.

To use the server from development or tooling, configure a client (for example in VS Code or a CLI) to point at the MCP endpoint served by the node process. The README demonstrates how to start the server locally (with npm) and how to load the MCP server into a client by providing the appropriate URL (e.g., http://localhost:3000/console-mcp-server/mcp) or by using the local MCP inspector at http://localhost:6274 to test discovery of tools and prompts without a full LLM environment.

Prerequisites:

• Node.js and npm installed (Node version as defined by the project, see .nvmrc if present)
• Docker (optional) for running a pre-built image

Install steps (Node.js path):

1. Install dependencies and build

npm ci
npm run build

2. Prepare environment

• Copy default.env to .env and edit values as needed

cp default.env .env

3. Run the MCP server locally

node mcp-server start --stdio --host=https://console.cloud.mia-platform.eu

Alternatively, run via npm scripts if provided by the project configuration:

npm run local:test

Docker path (optional):

• Use the Docker setup described in the related documentation (Docker hub image or custom image) and expose the required ports as configured by the environment and host runtime.

Environment variables are loaded automatically from a .env file if present. Key variables to consider:

• CONSOLE_HOST: required; the host address of the Mia-Platform Console instance.
• PORT: default is 3000; ensure the client configuration matches the running port or use the host flag to override.
• MIA_PLATFORM_CLIENT_ID and MIA_PLATFORM_CLIENT_SECRET: required if using a Service Account for machine-to-machine authentication; otherwise you can rely on user-based OAuth2 credentials.
• CLIENT_EXPIRY_DURATION: determines how long DCR-generated clients remain valid. If you encounter connectivity issues, verify that CONSOLE_HOST is reachable from the environment where the MCP server runs and that the port is not blocked by a firewall. The server loads environment variables from .env automatically, and you can override them at startup if needed.