Enables AI clients to interact with Mia-Platform Console APIs for advanced automation and management of platform resources.
Also known as mia-platform/console-mcp-server, @mia-platform/console-mcp-server
- Stars
- 3
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.2.2
- Last commit
- Nov 1, 2026
- License
- Apache-2.0
What is Mia-Platform Console MCP?
Mia-Platform Console enables AI clients to interact with Mia-Platform Console APIs for advanced automation and management of platform resources.
Summary generated from the project's README
About Mia-Platform Console MCP server
Automating the management of platform resources through Mia-Platform Console APIs is what this server enables for developers. By connecting AI clients like Claude Desktop, Cursor, or Visual Studio Code to your specific Mia-Platform instance, you can perform advanced operations directly through an LLM interface. The server supports both local execution via Node.js or Docker and remote connections through an HTTP setup.
Users can authenticate using a Service Account by providing a MIA_PLATFORM_CLIENT_ID and MIA_PLATFORM_CLIENT_SECRET for machine-to-machine tasks. Alternatively, the server supports OAuth2.1 and Dynamic Client Registration, allowing clients to discover authentication endpoints and guide users through a standard login process. You must configure the CONSOLE_HOST environment variable to point to your specific instance host address to establish a connection.
What you can do with it
- 1Perform machine-to-machine operationsUse a service account to allow an AI agent to execute operations on a company level without manual user login.
- 2Test tool discovery locallyDevelopers can verify that their tools and prompts are correctly implemented using the MCP inspector before deploying to a live LLM environment.
Written from the project's README. Every use case is checked against a quote from it.
How to install Mia-Platform Console MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Mia-Platform Console MCP in Claude Code
$ claude mcp add console-mcp-server -- npx -y @mia-platform/console-mcp-serverInstall Mia-Platform Console MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"console-mcp-server": {
"command": "npx",
"args": [
"-y",
"@mia-platform/console-mcp-server"
]
}
}
}Install Mia-Platform Console MCP in VS Code
.vscode/mcp.json
{
"servers": {
"console-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mia-platform/console-mcp-server"
]
}
}
}Install Mia-Platform Console MCP in VS Code CLI
$ code --add-mcp '{"name":"console-mcp-server","type":"stdio","command":"npx","args":["-y","@mia-platform/console-mcp-server"]}'Install Mia-Platform Console MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"console-mcp-server": {
"command": "npx",
"args": [
"-y",
"@mia-platform/console-mcp-server"
]
}
}
}Install Mia-Platform Console MCP in Codex
$ codex mcp add console-mcp-server -- npx -y @mia-platform/console-mcp-serverInstall Mia-Platform Console MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.console-mcp-server] command = "npx" args = ["-y", "@mia-platform/console-mcp-server"]
Install Mia-Platform Console MCP in Gemini CLI
$ gemini mcp add -s user console-mcp-server npx -- -y @mia-platform/console-mcp-serverInstall Mia-Platform Console MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"console-mcp-server": {
"command": "npx",
"args": [
"-y",
"@mia-platform/console-mcp-server"
]
}
}
}Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablemia-platform/console-mcp-server is public and reachablegithub.com/mia-platform/console-mcp-server ↗Pass
- Package names this repository as its source@mia-platform/console-mcp-server names mia-platform/console-mcp-server as sourcenpmjs.com/package/@mia-platform/console-mcp-server ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @mia-platform/console-mcp-servernpmjs.com/package/@mia-platform/console-mcp-server/v/1.2.2#p ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-01github.com/mia-platform/console-mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @mia-platform/console-mcp-serverPass
- No critical advisory in the package or its dependencies154 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeEndpoint did not answer initialize: HTTP 405Finding
README
View on GitHubMia-Platform Console MCP Server
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_IDandMIA_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:
npm ci
npm 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
.envfile if present in the project root. You can create one by copyingdefault.envto.envand 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:
node mcp-server startThen add the mcp server to your client simply including the url. As example for VS Code:
{ "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 variablePORT. More detail in the Environment Variables section.
Environment Variables
Environment variables located inside a file named .env are automatically included at service startup.
| Variable Name | Description | Required | Default Value |
|---|---|---|---|
LOG_LEVEL |
Log level of the application | No | info |
PORT |
Port number for the HTTP server | No | 3000 |
CONSOLE_HOST |
The host address of the Mia-Platform Console instance | Yes | - |
MIA_PLATFORM_CLIENT_ID |
Client ID for Service Account authentication | No | - |
MIA_PLATFORM_CLIENT_SECRET |
Client secret for Service Account authentication | No | - |
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. | No | 300 |
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:
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.
cp default.env .env
Finally to verify everything works, run:
npm run local:test
If you are not targeting the Console Cloud installation you can use the --host flag and specify your own host
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:
npm test
Or running a test for a single file run:
node --test --import tsx <FILE_PATH>
Mia-Platform Console MCP questions
How do I add Mia-Platform Console MCP to Claude Code?
Run claude mcp add console-mcp-server -- npx -y @mia-platform/console-mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add Mia-Platform Console MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How can I authenticate using a Service Account?
You can use a Service Account for machine-to-machine authentication by providing the MIA_PLATFORM_CLIENT_ID and MIA_PLATFORM_CLIENT_SECRET environment variables.