MCP Server & Middleware

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.