openrpc-mpc-server
# OpenRPC MCP Server
A Model Context Protocol (MCP) server that provides JSON-RPC functionality through [OpenRPC](https://open-rpc.org).
https://github.com/user-attachments/assets/3447175a-f921-4ded-8250-b611edb2fb67
## Features
### Tools
- `rpc_call` - Call arbitrary JSON-RPC methods
- Specify server URL, method name, and parameters
- Returns JSON-formatted results
- `rpc_discover` - Discover available JSON-RPC methods
- Uses OpenRPC's `rpc.discover` specification
- Lists all methods on a given server
## Development
Install dependencies:
```bash
npm install
```
Build the server:
```bash
npm run build
```
For development with auto-rebuild:
```bash
npm run watch
```
## Installation
To use with Claude Desktop, add the server config:
On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"openrpc": {
"command": "npx",
"args": ["-y", "openrpc-mcp-server"]
}
}
}
```
### Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector):
```bash
npm run inspector
```
The Inspector will provide a URL to access debugging tools in your browser.
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: rpc_call is for executing arbitrary JSON-RPC methods, while rpc_discover is specifically for server discovery to list available methods. There is no overlap in functionality, making them easy to distinguish.
Both tools follow a consistent 'rpc_' prefix pattern with descriptive suffixes (call, discover), using snake_case throughout. This provides a predictable and readable naming convention across the tool set.
With only 2 tools, the server feels minimal but appropriate for its narrow scope of JSON-RPC interaction. However, it lacks tools for common operations like server health checks or parameter validation, which could enhance usability in this domain.
The tools cover the core actions of calling methods and discovering server capabilities, which aligns with the OpenRPC domain. However, there are notable gaps such as error handling tools, batch request support, or schema validation that would provide more comprehensive coverage for JSON-RPC workflows.