Mia-Platform Catalog MCP Server

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

Setup

Most MCP clients require a configuration file to be created or modified to add the MCP server. The configuration file syntax can be different across clients. Please refer to the following links for the latest expected syntax:

• Windsurf (https://docs.windsurf.com/windsurf/mcp),
• VSCode (https://code.visualstudio.com/docs/copilot/chat/mcp-servers),
• Claude Desktop (https://modelcontextprotocol.io/quickstart/user),
• Cursor (https://docs.cursor.com/context/model-context-protocol).

For a list of clients that support MCP, see MCP Clients.

Option 1: connect to the remote MCP Server

A demo version of the Catalog MCP Server is reachable over HTTP at https://catalog.mia-demo-re5gu6.gcp.mia-platform.eu/mcp.

Important

The authorization server does not currently support Dynamic Client Registration. To authenticate your MCP client, use the client id catalog-mcp with no client secret.

You will need a Mia-Platform internal account to use the remote MCP Server.

{
  "servers": {
    "catalog": {
      "type": "http",
      "url": "https://catalog.mia-demo-re5gu6.gcp.mia-platform.eu/mcp"
    }
  },
  "inputs": []
}

Option 2: run with Docker

You can run the Catalog MCP Server in a Docker container, which provides isolation and doesn't require a local Rust installation.

{
  "servers": {
    "catalog": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--name", "catalog-mcp-server",
        "ghcr.io/mia-platform/catalog-mcp-server:latest",
        "--stdio",
        "--base-url=<catalog-base-url>"
      ]
    }
  },
  "inputs": []
}

Options 3: run from binary

Coming soon...

Configuration

The service acts as a proxy to the Mia-Platform Catalog, automatically generating the available tools from the Catalog OpenAPI specification.

Therefore, the service needs to known the URL on which the Catalog can be reached (--base-url CLI flag), and the OpenAPI specification to use (--spec CLI flag). By default, the spec is fetched from the Catalog itself. Otherwise, you can instruct the service to source it from a path on the filesystem or from a remote URL.

Environment variables

The service accepts the following environment variables:

Name	Type	Required	Default	Description
LOG_LEVEL	trace | debug | info | warn | error		info	The log level.

CLI options

The service can be configured with the following set of CLI arguments:

Flag	Required	Default	Description
-s, --spec <LOCATION>		<base-url>/openapi/json	Path or URL to the OpenAPI specification file from which the MCP server should be built.
-b, --base-url <URL>	✓		Mia-Platform Catalog base URL.
--stdio		false	Use stdio transport instead of HTTP streaming. When enabled, the server runs in stdio mode.
--api-prefix <PREFIX>		/	Prefix for the MCP server REST API (only applicable in HTTP mode).
-p, --port <PORT>		8000	Port to bind the MCP server to (only applicable in HTTP mode).
--ip <IP>		0.0.0.0	IP address to bind the MCP server to (only applicable in HTTP mode).

Contributing

Contributions are welcome! Please check the Contributing for guidelines on local development, standards, and other useful information.