Rierino MCP Middleware
Low-code MCP server development on a scalable microservices architecture.
What is Rierino?
Rierino is a low-code development platform that enables users to create scalable MCP servers using microservices architectures with ease.
How to use Rierino?
Developers can configure Rierino to build their MCP servers by defining services, selecting flows, and mapping sagas as tools. The platform supports various protocols like REST, event streaming and WebSocket for triggering these services.
Key features of Rierino?
- Low-code development for creating MCP servers
- Scalable microservices architecture
- Support for multiple protocols (REST, WebSocket, Event Streaming)
- Easy configuration of services and tools through a user-friendly interface
Use cases of Rierino?
- Building custom APIs for business applications
- Integrating machine learning models into existing workflows
- Creating event-driven architectures for real-time data processing
FAQ from Rierino?
- Can Rierino be used for any type of application?
Yes! Rierino is versatile and can be used for various applications requiring microservices and low-code solutions.
- Is Rierino suitable for non-developers?
Yes! Rierino's low-code approach makes it accessible for users with minimal coding experience.
- How does Rierino ensure security?
Rierino maintains existing security policies and user roles while allowing for flexible service configurations.
Rierino provides ability to service all of its functionality over Model Context Protocol (MCP), with a simple configuration that allows selection of flows to be serviced as tools over MCP, while maintaining already existing security policies and users roles. Any API, event processing or CDC flow can be included as MCP server tools and triggered using any protocol already supported by Rierino (e.g. REST, WebSocket, Event Streaming), going beyond the standard MCP implementations.
MCP servers can be built from scratch, using functionality such as database access, business rule evaluation, ML model prediction, external REST API calls, or could access 3rd party MCP servers acting as a middleware based on request details.
Model context protocol can be enabled on any microservice, allowing distributed execution of MCP requests in a scalable and high availability architecture by creating an Mcp Server Event Handler.
MCP server definitions allow configuration of services that are available through model context protocol through simple mapping of sagas as tools. Initial definition of a server includes:
- Name: A descriptive name
- Description: Detailed description of the server
- Tags: Descriptive tags for the server
- Status: Whether this server should be deployed or not
- Version: Current version of the server
- Domain: Categorization of the server based on business domain
- Comments: Historical list of comments, which typically includes information on server releases
- Parameters: Server asset configurations such as tools
For learning more about Rierino, please visit https://rierino.com.