OpenLegacy MCP Endpoint

Starting from OpenLegacy version 3.0.23, developers can effortlessly unlock new integration capabilities by exposing an MCP endpoint for their APIs.
This enhancement empowers teams to seamlessly connect, extend, and automate their low-code and no-code APIs with minimal setup - enabling faster innovation and easier interoperability across systems.

What is MCP?

MCP (Modular Connectivity Protocol) is a lightweight, standardized communication layer that simplifies how applications exchange data and services across diverse environments.
In the context of OpenLegacy, MCP provides a unified mechanism for exposing and consuming APIs, enabling external clients, systems, or automation platforms to interact with your OpenLegacy APIs without additional middleware or integration layers.

Why use MCP?

By exposing your OpenLegacy API through the MCP endpoint, you gain:

Simplified Integration: No need for complex routing or service adapters — external clients can connect directly via a consistent API interface.
Faster Connectivity: Makes your APIs instantly usable in automation workflows or other OpenLegacy components.
Low-code/No-code Enablement: Perfectly complements low-code and no-code projects that demand immediate connectivity with minimal DevOps effort.
Future-Ready Architecture: Leverages OpenLegacy’s interoperable design to support modular, service-based modernization strategies.

Overview

Once enabled, the MCP endpoint is automatically available under the /mcp path of your API service, providing a dedicated channel for standardized API interactions.

Enabling the MCP Endpoint

To enable the MCP endpoint, set the following environment variable before starting your API:

OL_FLOW_ENABLE_MCP=true

No further configuration is required - OpenLegacy will expose the endpoint automatically when the API starts.

Accessing the Endpoint

After your API starts successfully, the MCP endpoint can be accessed at:

https://<your-api-domain>/mcp

Example Configuration

You can enable the endpoint in your runtime environment, such as in a Docker container or Kubernetes deployment:

env:
  - name: OL_FLOW_ENABLE_MCP
    value: "true"

Requirements

OpenLegacy version 3.0.23 or later
Compatible low-code or no-code API project

Notes

If the environment variable is not set (or set to any value other than true), the /mcp endpoint will not be exposed.
No source code changes are required to enable this feature - only the environment variable configuration is needed.