Rierino

🚀 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.

🚀 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:

For more information, please visit https://rierino.com.