Console MCP server
online · 100% uptimeio.github.mia-platform/console-mcp-server·v1.2.2·3 starsThe official MCP Server from Mia-Platform to interact with Mia-Platform Console
3 stars
Reviews
Write oneNobody has reviewed Console yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Console tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- Code scan38 source files scanned25/25
- Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx</center> </body> </html> 0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableStreamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx</center> </body> </html>
How Console compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 67/100
- higher than 25% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 145 ms
- faster than 74% of 30,031 servers
- GitHub stars
- 3
- more than 80% of 28,688 servers
Install Console in Claude Code, Cursor or VS Code
claude mcp add --transport http console-mcp-server https://console.cloud.mia-platform.eu/console-mcp-server/mcp
What the publisher says
From the Console repository's README, as published. We do not edit it. Read it on GitHub
Mia-Platform Console MCP Server
[![pipeline status][build-svg]][pipeline-link] [![license][license-svg]](./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 MIAPLATFORMCLIENTID and MIAPLATFORMCLIENTSECRET.
- 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:
npm ci
npm run buildThese 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:
{
"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.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Console: common questions
- Is Console MCP server safe?
- With care: it is graded C, so read the findings first (67/100). Read the Console safety report
- How do I install Console?
- It runs remotely at console.cloud.mia-platform.eu. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Console need an API key?
- Yes. The registry entry asks for
Authorization. - Is Console maintained?
- The last commit was 34 days ago (2026-10-01). The latest release is v1.2.2.
- Is Console up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Console compare with other MCP servers?
- safety score 67/100 (higher than 25% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 145 ms (faster than 74% of 30,031 servers). Full comparison.