Console MCP Server

The official MCP Server from Mia-Platform to interact with Mia-Platform Console. The console mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

[pipeline status][build-svg]][pipeline-link] [license][license-svg]](./LICENSE)

The Mia-Platform Console MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with Mia-Platform Console APIs, enabling advanced automation and interaction capabilities for developers and tools.

Its toolset

Everything the assistant can do here goes through one of these:

• LOG_LEVEL — Log level of the application
• PORT — Port number for the HTTP server
• CONSOLE_HOST — The host address of the Mia-Platform Console instance
• MIA_PLATFORM_CLIENT_ID — Client ID for Service Account authentication
• MIA_PLATFORM_CLIENT_SECRET — Client secret for Service Account authentication
• CLIENT_EXPIRY_DURATION — Duration in seconds of clients generated with the DCR authentication flow. After this time, the client will be expired and cannot be used anylonger

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 4 environment variables: CONSOLE_HOST, MIA_PLATFORM_CLIENT_ID, MIA_PLATFORM_CLIENT_SECRET, FILE_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

To use the Mia-Platform Console MCP Server in your client (such as Visual Studio Code, Claude Desktop, Cursor, Gemini CLI or others), you first need to have a valid account on the Mia-Platform Console instance you want to communicate with. You will be required also to include the instance host address you in the environment variable named CONSOLE_HOST. You may decide to access via: - Service

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Console's toolset — LOG_LEVEL, PORT, CONSOLE_HOST and 3 more — is a fair guide to whether it matches your workflow. It is maintained by mia-platform; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the console mcp server does with a few real requests.