rpc_call
Call any JSON-RPC method on a server with parameters. A user would prompt: Call method <method> on <server url> with params <params>
Ask a JSON-RPC server which methods it publishes, then call any of them with your own parameters.
LABSCO SUMMARY
rpc_discover is what makes the pair worth installing: an OpenRPC-compliant server describes its own methods, so the next call is composed from that answer instead of from a README. Against a server that does not implement rpc.discover you are left with rpc_call and the method names you already knew.
A two-tool JSON-RPC client: rpc_discover for the method list a server describes about itself, rpc_call for any method on it.
The URL of a JSON-RPC server you can reach, and for the discovery call, one that implements rpc.discover. Apache-2.0 licensed.
One command — npx -y openrpc-mcp-server
USE CASES
Ask the server what it exposes, then call the method that looks right with the parameters its own description gave you — no client library in between.
Point discovery at the endpoint and read the method list, which settles whether the integration is worth starting before a line of it exists.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
rpc_callCall any JSON-RPC method on a server with parameters. A user would prompt: Call method <method> on <server url> with params <params>
rpc_discoverThis uses JSON-RPC to call rpc.discover which is part of the OpenRPC Specification for discovery for JSON-RPC servers. A user would prompt: What JSON-RPC methods does this server have? <server url>
BEFORE YOU INSTALL
2 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"openrpc-mcp-server": {
"command": "npx",
"args": [
"-y",
"openrpc-mcp-server"
]
}
}
}npx -y openrpc-mcp-server