MsgPack (LsMsgPack) MCP server

LsMsgPack

MsgPack serializers for .NET classes (like the xml and json serializers), with an optional indexed schema and type ids for polymorphic object models, ASP.NET formatters, and a MsgPack debugging and validation tool (MsgPack Explorer) that also works as a Fiddler plugin, a Visual Studio debugger visualizer and a VS Code extension.

More info about MsgPack Explorer (and screenshots) can be found at: http://www.infotopie.nl/open-source/msgpack-explorer

ASP.NET Integration

Three packages let ASP.NET controllers and HttpClient receive and return MsgPack the same way they handle JSON. Clients choose the format with the Content-Type and Accept headers: application/msgpack (or application/x-msgpack) for plain MsgPack that any implementation understands, or application/x-lsmsgpack for the indexed schema with type ids (smaller, polymorphic, and with the schema sent only once per client).

See docs/WebFormatters.md for the settings per media type, examples for each package, and how schemas are negotiated.

Client applications

The serializers run in any .NET client (WinForms, WPF, MAUI, Avalonia...). Save and load your documents with LtMsgPackSerializer.Serialize / Deserialize: with the default settings, files are smaller than JSON, keep loading when your classes gain or lose properties, and support polymorphic object models without extra attributes. To call a web service that uses the formatters above, use LsMsgPack.AspNet.WebApi with HttpClient, or serialize the bodies yourself for any other MsgPack server.

See docs/ClientApps.md for examples (files, web services, trimming).

Which package

There are two serializers. They write exactly the same data with the same settings and read each other's output:

• LtMsgPack (LtMsgPack): use this for normal use. It writes and reads directly from and to your objects. On the invoices of the benchmark it writes about 3-4x and reads about 4x as fast as System.Text.Json, with 35-47% smaller payloads. It also has presets for exchanging data with MessagePack-CSharp, Nerdbank.MessagePack and non-.NET libraries. The web formatters use it.
• LsMsgPack (LsMsgPack): use this when you really want to inspect MsgPack data in your app. It builds a tree of MsgPack items (maps, arrays, strings...) that you can walk, for any payload, also when you don't have the classes. That makes it much slower: about 2-4x slower than System.Text.Json.

NuGet packages

graph BT
  Core["LsMsgPack.Core<br/><i>settings, schema, type resolving</i>"]
  Ls["LsMsgPack<br/><i>item tree, inspecting</i>"]
  Lt["LtMsgPack<br/><i>fast serializer</i>"]
  AspNetCore["LsMsgPack.AspNetCore"]
  WebApi["LsMsgPack.AspNet.WebApi"]
  Mvc["LsMsgPack.AspNet.Mvc"]
  Mem(["System.Memory"])
  Unsafe(["System.Runtime.CompilerServices.Unsafe"])
  AspNetCoreFx(["Microsoft.AspNetCore.Mvc.Core 2.x /<br/>Microsoft.AspNetCore.App"])
  WebApiClient(["Microsoft.AspNet.WebApi.Client"])
  AspNetMvc(["Microsoft.AspNet.Mvc"])

Shortened. The full README is on GitHub.