Service MCP Requests

These actions provide ability to expose existing microservice capabilities over MCP.

Service MCP Requests Actions

CallRPC

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

Fields (table)

Field	Definition	Example	Default
Domain	ID of the MCP server to interact with	procurement_specialist	-
Input Element	Json path for the input in request event payload	message	-
Output Element	Json path for the output in response event payload	output	-

Fields (JSON Schema)

With event metadata parameters as:

Parameters (table)

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

Parameters (JSON Schema)

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": {}
    }
}