56 packages tagged with “json-rpc”
A .Net Core Client implementation for Json Rpc v2 requests.
A AspNet Core IRouter implementation for Json Rpc v2 requests for Microsoft.AspNetCore.Routing.
JSON-RPC implementation over HTTP.
Adds DataAnnotations validation to rpc calls
Simple JSON-RPC Client for .Net Core 1.0
An asynchronous JSON RPC server & client library.
Runtime dynamic client-side proxy builder for CXuesong.JsonRpc.Standard.
Json-Rpc implementation in .Net OWIN and TypeScript
Brotli compression library for EasyRpc.AspNetCore
HttpClient-based JsonRpcClientHandler for CXuesong.JsonRpc.Standard.
Stream-based server and client handler for CXuesong.JsonRpc.Standard.
Evolution allows companies to integrate applications on a global scale without complex infrastructure or software. It enables developers to rapidly and cost-effectively transition existing Windows desktop applications to a service or API-based model. Whether you are an independent software vendor transitioning to SaaS or corporate IT unifying your development efforts, implementing with an API-based model gives existing applications the ability to seamlessly integrate even if built with different programming languages. With Evolution, developers can create an API to expose the business rules developed in one language, such as DataFlex or C#, and have it available to be consumed by other languages via multiple protocols. The Evolution framework allows Windows developers to: - Build an API using many development languages (C#, Java, DataFlex, VB, etc) - Expose the API via HTTP or TCP/IP socket using multiple protocols (SOAP, JSON-RPC, Thrift binary, Thrift compact) - Deliver mobile, Web, or desktop application solutions - Serve the application with a web server (Apache or IIS) or standalone
Simple Odoo JSON-RPC Client for .Net Core 2.0. Fork from https://github.com/vmlf01/OdooRpc.CoreCLR.Client
Library providing common structures used for JSON-RPC protocol implementations. Code Entry Point: public class MyRequest : Request{}; public class MyResponse : ResultResponse{};
Simple Odoo JSON-RPC Client for .Net Core 1.0
Implements core business logic and application-level workflows.
Build Model Context Protocol (MCP) servers and clients in .NET with MCPSharp. Create MCP-compliant tools and functions that AI models can discover and use. Features easy to use attribute-based API allowing anyone to spin up a server in minutes, and a Microsoft.Extensions.AI compatible client that generates AIFunctions, ready to be consumed by any IChatClient or compatible system. await MCPServer.StartAsync("EchoServer", "1.0.0"); --- server: class MyTool { [McpTool("echo","returns the input string back to you")] public string echo(string input) => input; } ---client: var client = new MCPClient("MyClient","1.0.0", "EchoServer.exe" //or dotnet EchoServer.dll if you wish await client.CallToolAsync("echo", new Dictionary<string, object>{{"input", "input string to echo"}});
Log API Calls to Moesif API Analytics
ASP.NET Core support for CXuesong.JsonRpc.Standard.
Yet another JsonRPC Class Library for supporting Json-RPC APIs
A AspNet Core IRouter extension for Json Rpc v2 websocket based requests for Microsoft.AspNetCore.Routing.
A wallet and daemon client to interface with Monero's JSON-RPC API, built on .netstandard2.1.
.Net implementation of the Nimiq RPC client specs.
Simple Odoo JSON-RPC Client, adapted to .Net Core 3.1. Fork from https://github.com/vmlf01/OdooRpc.CoreCLR.Client
JsonRpc 2.0 Server for .NET
Contains the core JSON-RPC abstractions and building blocks of the A2A Protocol.
Mopidy Music Server control library. Connect by Http-Post/JSON-RPC, or WebSocket(limitted support). Implemented all methods on mopidy.core.
Json-RPC RT implements bidirectional JSON-RPC 2.0 protocol.
.NET Middleware to log API Calls to Moesif API Analytics and Monitoring