OpenRPC MCP Server
Connect your AI agents to any JSON-RPC-compatible API with OpenRPC MCP Server, supporting dynamic method discovery, remote procedure automation, and streamlined backend integration.

What does “OpenRPC” MCP Server do?
The OpenRPC MCP Server is a Model Context Protocol (MCP) server that provides JSON-RPC functionality via the OpenRPC specification. This server acts as a bridge between AI assistants and external JSON-RPC-enabled systems, enabling structured, programmable interactions with APIs and services that implement the JSON-RPC standard. By exposing tools like method discovery and remote procedure calls, the OpenRPC MCP Server empowers developers and AI agents to interact dynamically with various services, perform operations, and automate workflows. It enables tasks such as querying external systems, invoking custom methods, and integrating API-driven processes, thereby enhancing AI development workflows, debugging, and system integration.
List of Prompts
No prompt templates are mentioned in the repository.
List of Resources
No explicit MCP resources are listed in the repository.
List of Tools
- rpc_call
Call arbitrary JSON-RPC methods by specifying the server URL, method name, and parameters. Returns JSON-formatted results for integration and automation. - rpc_discover
Discover available JSON-RPC methods on a server using the OpenRPCrpc.discover
specification. Allows listing and exploring all supported methods on a given server.
Use Cases of this MCP Server
- API Integration
Use AI assistants to connect with any JSON-RPC-compatible API for tasks such as data retrieval, updating records, or triggering remote workflows. - Dynamic Service Discovery
Automatically discover and enumerate available methods on external JSON-RPC servers, streamlining integration and documentation. - Remote Procedure Automation
Enable LLMs or agents to execute remote procedures programmatically, automating backend operations and business logic execution. - Debugging and Development
Test and debug JSON-RPC endpoints with AI assistance, including auto-discovery and structured method invocation for rapid development. - Workflow Orchestration
Coordinate multiple JSON-RPC service calls within a broader automated workflow managed by AI agents.
How to set it up
Windsurf
- Ensure you have Node.js and npm installed.
- Locate your Windsurf configuration file.
- Add the OpenRPC MCP server configuration under the
mcpServers
object. - Use the following JSON snippet:
{
"mcpServers": {
"openrpc": {
"command": "npx",
"args": ["-y", "openrpc-mcp-server"]
}
}
}
- Save the configuration and restart Windsurf.
- Verify that the OpenRPC server is running and accessible.
Claude
- Make sure Node.js and npm are installed.
- Open the Claude configuration file:
- MacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
%APPDATA%/Claude/claude_desktop_config.json
- MacOS:
- Add the following configuration:
{
"mcpServers": {
"openrpc": {
"command": "npx",
"args": ["-y", "openrpc-mcp-server"]
}
}
}
- Save the file and restart Claude Desktop.
- Confirm the configuration is active.
Cursor
- Install Node.js and npm.
- Locate the Cursor MCP configuration file.
- Insert the following JSON in your configuration:
{
"mcpServers": {
"openrpc": {
"command": "npx",
"args": ["-y", "openrpc-mcp-server"]
}
}
}
- Save changes and restart Cursor.
- Check that the OpenRPC MCP server is connected.
Cline
- Ensure Node.js and npm are available.
- Find the Cline configuration file for MCP servers.
- Add the OpenRPC MCP server as shown:
{
"mcpServers": {
"openrpc": {
"command": "npx",
"args": ["-y", "openrpc-mcp-server"]
}
}
}
- Save and restart Cline.
- Validate the server connection.
Securing API Keys
To secure API keys, use environment variables and pass them via the configuration.
Example:
{
"mcpServers": {
"openrpc": {
"command": "npx",
"args": ["-y", "openrpc-mcp-server"],
"env": {
"MY_API_KEY": "your-api-key-here"
},
"inputs": {
"apiKey": "${MY_API_KEY}"
}
}
}
}
How to use this MCP inside flows
Using MCP in FlowHunt
To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:
{
"openrpc": {
"transport": "streamable_http",
"url": "https://yourmcpserver.example/pathtothemcp/url"
}
}
Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “openrpc” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.
Overview
Section | Availability | Details/Notes |
---|---|---|
Overview | ✅ | JSON-RPC bridge via OpenRPC |
List of Prompts | ⛔ | No prompt templates listed |
List of Resources | ⛔ | No explicit MCP resources listed |
List of Tools | ✅ | rpc_call , rpc_discover |
Securing API Keys | ✅ | Shown via env/inputs example |
Sampling Support (less important in evaluation) | ⛔ | Not mentioned |
Our opinion
This MCP server offers clear, practical tooling for JSON-RPC integration and method discovery, but lacks prompt and resource primitives. Security via environment variables is supported. Its documentation is concise. Overall, it provides robust core functionality but is somewhat barebones compared to more feature-rich MCPs.
MCP Score
Has a LICENSE | ✅ (Apache-2.0) |
---|---|
Has at least one tool | ✅ |
Number of Forks | 10 |
Number of Stars | 34 |
Frequently asked questions
- What is the OpenRPC MCP Server?
The OpenRPC MCP Server is a Model Context Protocol server that enables AI assistants to interact with external JSON-RPC-compatible systems. It provides method discovery and remote procedure call capabilities using the OpenRPC specification, making seamless API integration and automation possible.
- What tools does the OpenRPC MCP Server provide?
It includes `rpc_call` for invoking arbitrary JSON-RPC methods and `rpc_discover` for listing available methods on a server, supporting dynamic integration and automation.
- How can I secure my API keys when using this server?
API keys and sensitive credentials should be set as environment variables in your MCP server configuration. Use the `env` and `inputs` fields to reference these securely in your config files.
- What are common use cases for this MCP server?
Common uses include API integration, dynamic service discovery, remote procedure automation, debugging JSON-RPC endpoints, and orchestrating multi-step workflows with AI agents.
- Does the OpenRPC MCP Server support prompt templates or resource primitives?
No, this MCP server focuses on core JSON-RPC bridging and does not provide prompt templates or explicit MCP resources. It excels at method discovery and procedure execution.
Start Integrating with OpenRPC MCP Server
Empower your AI workflows with powerful JSON-RPC automation and dynamic API integrations using the OpenRPC MCP Server. Try it in FlowHunt today.