AgentRPC + Perplexity: Complete MCP Integration
AgentRPC is a MCP server that Connect to any function, any language, across network boundaries using AgentRPC..
When integrated with Perplexity, 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 Perplexity, 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 Perplexity
- 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
- Perplexity installed and configured
- Compatible operating system (macOS App)
Installation
Step 1: Install AgentRPC
Configuration
Step 2: Configure Perplexity
- Open Perplexity settings
- Navigate to MCP server configuration
- Add AgentRPC server with appropriate settings
- Save and restart if needed
Examples
Once configured, you can use AgentRPC in Perplexity:
Multi-Language Microservices
undefined
Ask Perplexity: "Call Python ML model from TypeScript app via Go API"
Expected Result: undefined
Cross-Cloud Function Calls
undefined
Ask Perplexity: "Execute distributed data processing across three clouds"
Expected Result: undefined
Kubernetes Function Registry
undefined
Ask Perplexity: "List available functions in production cluster"
Expected Result: undefined
Testing Your Setup
- Launch Perplexity
- Verify AgentRPC is available in the tools list
- Test basic AgentRPC functionality
Troubleshooting
Common Issues
Connector Fails to Start
Symptoms: Status remains "Inactive" or shows error, Red dot indicator
Cause: Command not found or missing dependencies in the environment.
Solution:
- Test the command in a regular terminal window to ensure it works.
- Use absolute paths for all executables (e.g., use
/opt/homebrew/bin/nodeinstead ofnode). - Check if the server requires specific environment variables.
Permission Errors
Symptoms: "Access denied" responses, Server crashes on file access
Cause: macOS permissions blocking access to specific folders.
Solution:
- Ensure Perplexity (or the terminal running the server) has Full Disk Access in macOS System Settings if accessing sensitive directories.
- Verify PerplexityXPC is correctly installed.
Tools Not Visible
Symptoms: Perplexity does not attempt to use the tool, Hallucinated responses
Cause: Connector not selected as a source.
Solution:
- Start a NEW thread.
- Explicitly select the connector in the "Sources" menu before sending the prompt.
AgentRPC not appearing in Perplexity
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check AgentRPC installation
- Restart Perplexity
- Check logs for error messages
Next Steps
Now that AgentRPC is integrated with Perplexity:
- Explore all AgentRPC capabilities through Perplexity
- Check out other MCP servers that work with Perplexity
- Join the MCP community for tips and support
- Consider contributing to AgentRPC development
Need Help?
- Search for AgentRPC documentation
- Check the Perplexity MCP guide
- Join the MCP community discussions