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.
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.
For a detailed description on how to connect to the remote Mia-Platform Catalog server, refer to the official documentation.
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.
The service accepts the following environment variables:
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| LOG_LEVEL | trace | debug | info | warn | error |
info |
The log level. |
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. When loading from the filesystem, the file extension must be .json, .yaml, or .yml. |
|
-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). | |
--allowed-hosts [HOST]... |
localhost, 127.0.0.1, ::1 |
Allowed hostnames or host:port authorities for inbound Host header validation (only applicable in HTTP mode). If omitted, defaults to loopback hosts only. Pass with no values to allow any host. |
Contributions are welcome! Please check the Contributing for guidelines on local development, standards, and other useful information.