agentrpc/agentrpc

> Universal RPC layer for AI agents across network boundaries and languages
Overview
AgentRPC allows you to connect to any function, in any language, across network boundaries. It's ideal when you have services deployed in:
- Private VPCs
- Kubernetes clusters
- Multiple cloud environments
AgentRPC wraps your functions in a universal RPC interface, connecting them to a hosted RPC server accessible through open standards:
- Model Context Protocol (MCP)
- OpenAI-compatible tool definitions (OpenAI, Anthropic, LiteLLM, OpenRouter, etc.)
How It Works
1. **Registration**: Use our SDK to register functions and APIs in any language
2. **Management**: The AgentRPC platform (api.agentrpc.com) registers the function and monitors its health
3. **Access**: Receive OpenAPI SDK compatible tool definitions and a hosted MCP server for connecting to compatible agents
Key Features
| Feature | Description |
|---------|-------------|
| **Multi-language Support** | Connect to tools in TypeScript, Go, Python and .NET (coming soon) |
| **Private Network Support** | Register functions in private VPCs with no open ports required |
| **Long-running Functions** | Long polling SDKs allow function calls beyond HTTP timeout limits |
| **Full Observability** | Comprehensive tracing, metrics, and events for complete visibility |
| **Automatic Failover** | Intelligent health tracking with automatic failover and retries |
| **Framework Compatibility** | Out-of-the-box support for MCP and OpenAI SDK compatible agents |
Getting Started
Quick Start
Follow the quick start example on our docs site.
Examples
Explore working examples in the examples directory.
MCP Server
The AgentRPC TypeScript SDK includes an optional MCP (Model Context Protocol) server.
This launches an MCP-compliant server for external AI models to interact with your registered tools.
Claude Desktop Integration
Add to your claude_desktop_config.json:
More Info
Cursor Integration