Console Mcp Server

io.github.mia-platformPublished by GitHub account mia-platformv1.2.2Updated Nov 2, 2026

The official MCP Server from Mia-Platform to interact with Mia-Platform Console

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Official Mia-Platform MCP server that connects an assistant to Mia-Platform Console APIs for automation and interaction on the Console instance you configure.

What you can do
  • Connect to a Mia-Platform Console instance and expose its APIs to the assistant for automation and interaction.
  • Authenticate either with a Service Account (client ID and secret) or through the OAuth2.1 / Dynamic Client Registration flow with your own user credentials.
  • Run as a remote HTTP endpoint, a local Node.js process over stdio, or a local HTTP server on a configurable port.
  • The README does not list individual tools, so the exact operations available depend on the Console instance and the account's permissions.
When to use it
Useful when you work with Mia-Platform Console and want an assistant to automate or interact with your company's Console resources instead of doing it by hand in the web UI.
Requirements
A valid account on the target Mia-Platform Console instance and the instance host address in CONSOLE_HOST (or the --host flag). For Service Account access, MIA_PLATFORM_CLIENT_ID and MIA_PLATFORM_CLIENT_SECRET. Local runs need Node.js (npm ci, npm run build) or Docker; optional PORT, LOG_LEVEL and CLIENT_EXPIRY_DURATION. Remote clients send a bearer token in the Authorization header.
Before you install
The server acts on your Console company with the permissions of the account or Service Account used, so it can change real resources; a Service Account gets full access to the company it was created in. Treat MIA_PLATFORM_CLIENT_SECRET and the Authorization token as secrets. DCR-generated clients expire after CLIENT_EXPIRY_DURATION (default 300 seconds). A .env file in the project root is loaded automatically.

Installation

In SourceWeft

  1. Open Console Mcp Server in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mia-platform%2Fconsole-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "console": {
      "type": "http",
      "url": "https://console.cloud.mia-platform.eu/console-mcp-server/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Mia-Platform Console MCP Server

[pipeline status] [license]

Introduction

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.

Prerequisites

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 Account to perform machine-2-machine authentication and have full access to the MCP capabilities to perform operations on the Company where the S.A. has been created (for more information, visit our official documentation on how to create a Mia-Platform Service Account). If you do so, you need to include the environment variables MIA_PLATFORM_CLIENT_ID and MIA_PLATFORM_CLIENT_SECRET.
  • Using your own credentials: Mia-Platform Console MCP Server follows the Model Context Protocol specifications on authentication using OAuth2.1 and Dynamic Client Registration: clients that follow that specifications will be able to discover the authentication endpoints of the selected Mia-Platform instance you want to access to and guide you to perform the log in.

How to Run

You can run stable versions of the Mia-Platform Console MCP Server using Docker. You can get detailed guide in the related page of the Mia-Platform documentation.

If you don't have Docker installed, or you simply wish to run it locally, you can use NPM and Node.js. Once you have cloned the project you can run the commands:

sh
npm cinpm run build

These commands will install all the dependencies and then transpile the typescript code in the build folder.

NOTE

The server automatically loads environment variables from a .env file if present in the project root. You can create one by copying default.env to .env and updating the values as needed.

Once these steps are completed you can setup the MCP server using the node command like the following:

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

TIP

Alternatively, you start the service after the build with the following command:

sh
node mcp-server start

Then add the mcp server to your client simply including the url. As example for VS Code:

json
{  "mcp": {    "servers": {      "mia-platform-console": {        "type": "http",        "url": "http://localhost:3000/console-mcp-server/mcp"      }    }  }}

Instead of 3000, please include the port defined in the environment variable PORT. More detail in the Environment Variables section.

Environment Variables

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

Variable NameDescriptionRequiredDefault Value
LOG_LEVELLog level of the applicationNoinfo
PORTPort number for the HTTP serverNo3000
CONSOLE_HOSTThe host address of the Mia-Platform Console instanceYes-
MIA_PLATFORM_CLIENT_IDClient ID for Service Account authenticationNo-
MIA_PLATFORM_CLIENT_SECRETClient secret for Service Account authenticationNo-
CLIENT_EXPIRY_DURATIONDuration in seconds of clients generated with the DCR authentication flow. After this time, the client will be expired and cannot be used anylonger.No300

Local Development

To help with the development of the server you need Node.js installed on your machine.
The recommended way is to use a version manager like nvm or mise.

Once you have setup your environment with the correct Node.js version declared inside the .nvmrc file you can run the following command:

sh
npm ci

Once has finished you will have all the dependencies installed on the project, then you have to prepare an environment file by copying the default.env file and edit it accordingly.

sh
cp default.env .env

Finally to verify everything works, run:

sh
npm run local:test

If you are not targeting the Console Cloud installation you can use the --host flag and specify your own host

sh
npm run local:test  -- --host https://CONSOLE_HOST

This command will download and launch the MCP inspector on http://localhost:6274 where you can test if the implementation will work correctly testing the discovery of tools and prompts without the needs of a working llm environment.

To run tests for new implementations you can use:

sh
npm test

Or running a test for a single file run:

sh
node --test --import tsx <FILE_PATH>

Source: README.md at commit 18f6855

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.2.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts