Service MCP Requests

This handler (com.rierino.handler.mcp.McpServerEventHandler) provides ability to utilize existing microservice capabilities to be serviced over MCP to clients

Handler Parameters

Parameter	Definition	Example	Default
server.state	Name of the state manager with MCP server configurations	mcp_server	genai_model
server.domain	Name of the server domain to include (for filtering server.state records)	procurement	-
saga.handler	Name of the saga event handler that executes tool sagas	ai_saga	saga
saga.state	Name of the state manager with saga definitions (used as tools)	ai_saga	saga

Servers

Servers used by this event handler are stored in a regular state manager as defined in MCP Servers section.

Actions

CallRPC

Responds to a request using MCP protocol. Event metadata fields applicable for this action are as follows:

Field	Definition	Example	Default
domain	ID of the MCP server to interact with	procurement_specialist	-
inputElement	Json path for the input in request event payload	message	-
outputElement	Json path for the output in response event payload	output	-

With event metadata parameters as:

Parameter	Definition	Example	Default
inputPattern	Jmespath expression for converting input payload to MCP call	-	-

Input contents should match MCP server calls such as:

Initialize Request

{
    "jsonrpc": "2.0",
    "method": "initialize"
}

Tool Listing Request

{
    "jsonrpc": "2.0",
    "method": "tools/list"
}

Tool Call Request

{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params":{
        "name": "Hello",
        "arguments": {}
    }
}

For more information on MCP:

Introduction - Model Context ProtocolModel Context Protocol

Model Context Protocol Introduction