Rierino

Rierino provides a multi - functional service based on the MCP protocol, supporting flexible configuration and distributed execution.

Developer tools Cloud platform #Protocol service #Distributed #Middleware #Microservice

rating : 2 points

downloads : 23

update time : 2025-04-28

What is the Rierino MCP Server?

The Rierino MCP Server is a middleware service based on the Model Context Protocol (MCP). It allows various business processes (such as API calls, event handling, or CDC processes) to be exposed as tools through the MCP protocol. These tools can be triggered through any protocol supported by Rierino (such as REST, WebSocket, event streams).

How to use the Rierino MCP Server?

To use the MCP Server, you need to first define the server configuration, including selecting the processes to be exposed as tools. After the configuration is completed, you can call these tools through the supported protocols. The server can run as an independent service or as middleware to access third - party MCP servers.

Applicable scenarios

It is suitable for scenarios where a unified interface is required to access multiple business processes, especially in distributed systems where existing security policies and user roles need to be maintained.

Main features

Multi - protocol supportSupports triggering MCP tools through multiple protocols such as REST, WebSocket, and event streams

Distributed executionThe MCP protocol can be enabled on any microservice to achieve a distributed, scalable, and highly available architecture

Flexible configurationYou can easily configure which processes are exposed as tools while maintaining existing security policies

Middleware functionIt can be used as middleware to access third - party MCP servers

Advantages and limitations

Advantages

Unified interface to access multiple business processes

Maintain existing security policies and user roles unchanged

Support distributed execution to improve scalability and availability

Flexible configuration options

Limitations

It requires a certain learning cost to understand the MCP protocol

Configuring complex business processes may require professional knowledge

How to use

Define the MCP server configuration

Create a new MCP server definition, including basic information such as name, description, and tags

Select the processes to be exposed

Select which API, event handling, or CDC processes are to be exposed as MCP tools in the configuration

Configure server parameters

Set the server asset configuration, such as tool parameters

Deploy the server

Deploy the configured MCP server to the production environment

Usage examples

Database access serviceExpose the database access process as an MCP tool, allowing front - end applications to query the database through the REST API

Machine learning prediction serviceExpose the machine learning model prediction process as an MCP tool, allowing real - time prediction results to be obtained through WebSocket

Frequently Asked Questions

What is the difference between an MCP server and an ordinary API server?

How to ensure the security of the MCP server?

Can multiple MCP servers run simultaneously?

Related resources

Rierino official documentation

Detailed technical documentation for the MCP server

Rierino official website

The official website of the Rierino product

🚀 MCP Server and Middleware

Rierino provides the ability to offer all functionalities through the Model Context Protocol (MCP). You can achieve this by simply configuring the service processes you want to use as tools while maintaining existing security policies and user roles.

MCP Server Configuration

🚀 Quick Start

Rierino enables the provision of all features via the Model Context Protocol (MCP). It allows you to select service processes as tools through simple configuration while maintaining existing security policies and user roles. Any API, event handling, or CDC process can be configured as a tool on the MCP server and triggered using protocols already supported by Rierino (e.g., REST, WebSocket, event streams), thus going beyond the standard MCP implementation.

✨ Features

Flexible Construction: The MCP server can be built from scratch, leveraging functions such as database access, business rule evaluation, machine learning model prediction, and external REST API calls. Alternatively, it can access third - party MCP servers as middleware to handle requests based on request details.
Distributed Execution: By creating a dedicated "Mcp Server Event Handler", the model context protocol can be enabled on any microservice, enabling distributed execution and running MCP requests in a scalable and highly available architecture.
Configurable Services: The MCP server definition allows the configuration of services accessible via the model context protocol by mapping orchestration processes (sagas) as tools.

📚 Documentation

The initial server definition includes the following information:

Property	Details
Name	Descriptive name
Description	Detailed server description
Tags	Descriptive tags
Status	Whether the server should be deployed
Version	Current version number
Domain	Classification based on the business domain
Comments	A list of historical notes containing server release information
Parameters	Server asset configuration, such as tools