AgentRPC + MCP Inspector: Complete MCP Integration

AgentRPC is a MCP server that Connect to any function, any language, across network boundaries using AgentRPC..

When integrated with MCP Inspector, you can:

• Register functions across languages and networks
• Call functions across network boundaries
• List all registered functions across languages

This guide provides step-by-step instructions to set up AgentRPC in MCP Inspector, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• AgentRPC will be fully integrated and operational
• You can use AgentRPC tools directly in MCP Inspector
• All AgentRPC capabilities will be available for your workflows
• Access to 4 different tools

Prerequisites

Before starting, ensure you have:

• API secret from AgentRPC dashboard
• MCP Inspector installed and configured
• Compatible operating system (CLI Tool)

Installation

Step 1: Install AgentRPC

Configuration

Step 2: Configure MCP Inspector

1. Open MCP Inspector settings
2. Navigate to MCP server configuration
3. Add AgentRPC server with appropriate settings
4. Save and restart if needed

Examples

Once configured, you can use AgentRPC in MCP Inspector:

Multi-Language Microservices

undefined

Ask MCP Inspector: "Call Python ML model from TypeScript app via Go API"

Expected Result: undefined

Cross-Cloud Function Calls

undefined

Ask MCP Inspector: "Execute distributed data processing across three clouds"

Expected Result: undefined

Kubernetes Function Registry

undefined

Ask MCP Inspector: "List available functions in production cluster"

Expected Result: undefined

Testing Your Setup

1. Launch MCP Inspector
2. Verify AgentRPC is available in the tools list
3. Test basic AgentRPC functionality

Troubleshooting

Common Issues

Connection Failed

Symptoms: Inspector UI shows "Disconnected"

Cause: Server process exited or failed to start.

Solution:

• Check the terminal where you ran npx ... for error output from your server.
• Ensure your server prints JSON-RPC messages to stdout.

Tools Not Showing

Symptoms: Tool list is empty

Cause: Server did not send tools/list response or capabilities negotiation failed.

Solution:

• Check the "Console" or "Logs" tab in the Inspector to see the raw communication.
• Verify your server code correctly implements the ListToolsRequest handler.

AgentRPC not appearing in MCP Inspector

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check AgentRPC installation
• Restart MCP Inspector
• Check logs for error messages

Next Steps

Now that AgentRPC is integrated with MCP Inspector:

• Explore all AgentRPC capabilities through MCP Inspector
• Check out other MCP servers that work with MCP Inspector
• Join the MCP community for tips and support
• Consider contributing to AgentRPC development

Need Help?

• Search for AgentRPC documentation
• Check the MCP Inspector MCP guide
• Join the MCP community discussions