Console Mcp Server

io.github.mia-platform由 GitHub 账号 mia-platform 发布v1.2.2更新于 Nov 2, 2026

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

已验证Streamable HTTP可网页运行云端与基础设施开发者工具

概览

AI 生成的概览

Mia-Platform 官方 MCP 服务器，让助手连接 Mia-Platform Console API，在你配置的 Console 实例上实现自动化与交互。

可以做什么
  • 连接 Mia-Platform Console 实例，把其 API 暴露给助手用于自动化与交互。
  • 支持用 Service Account（客户端 ID 与密钥）认证，或通过 OAuth2.1 与动态客户端注册流程用个人凭据登录。
  • 可作为远程 HTTP 端点、本地 Node.js stdio 进程，或运行在可配置端口上的本地 HTTP 服务。
  • README 未列出具体工具，可用操作取决于 Console 实例及账号权限。
适用场景
适合在使用 Mia-Platform Console 时，希望助手代为自动化或操作公司 Console 资源，而不必在网页界面手动完成的场景。
运行要求
需要目标 Mia-Platform Console 实例上的有效账号，并通过 CONSOLE_HOST（或 --host 参数）提供实例地址。使用 Service Account 时需 MIA_PLATFORM_CLIENT_ID 与 MIA_PLATFORM_CLIENT_SECRET。本地运行需 Node.js（npm ci、npm run build）或 Docker；可选 PORT、LOG_LEVEL、CLIENT_EXPIRY_DURATION。远程客户端需在 Authorization 头中发送 bearer 令牌。
安装前请注意
服务器以所用账号或 Service Account 的权限操作 Console 公司资源，可能改动真实资源；Service Account 对其所在公司拥有完整访问权限。请将 MIA_PLATFORM_CLIENT_SECRET 与 Authorization 令牌视为机密。动态注册生成的客户端在 CLIENT_EXPIRY_DURATION（默认 300 秒）后过期。项目根目录的 .env 文件会被自动加载。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Console Mcp Server，将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.mia-platform%2Fconsole-mcp-server/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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>

来源：README.md，提交 18f6855

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v1.2.2最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分