GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Decodes MsgPack (LsMsgPack schemas, type ids) as text and reads it from variables while debugging.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"lsmsgpack": {
"command": "dnx",
"args": [
"LsMsgPack.Mcp",
"--yes"
]
}
}
}在终端中运行这条命令
claude mcp add lsmsgpack -- dnx LsMsgPack.Mcp --yes粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"lsmsgpack": {
"command": "dnx",
"args": [
"LsMsgPack.Mcp",
"--yes"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"lsmsgpack": {
"type": "stdio",
"command": "dnx",
"args": [
"LsMsgPack.Mcp",
"--yes"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 mlsomers 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(2026.11.6.1)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 .NET。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MsgPack for AI agents. An MCP server and a command line tool that decode MsgPack data into text an AI (or a person in a terminal) can read, and that read the bytes of a variable of a program paused in the debugger of VS Code or Visual Studio.
Language models read text, not bytes. Hex or base64 costs several tokens per byte, and decoding it by hand is slow and error-prone. Some data can't be decoded from the bytes at all: LsMsgPack's indexed schema writes property names as indexes, and a schema reference holds only the 16-byte id of the schema. This tool decodes the data with the LsMsgPack library itself (the code of MsgPack Explorer) and writes it as JSON with comments:
MsgPack "doc1" 247 bytes from payload (byte[], Launch Api).
Structure: indexed schema (inline, 3 types) followed by the body No errors, 0 warnings or comments. Schema (inline): type ids and property ids in the body are indexes into these lists. #0 Invoice: Id, Customer, Billing, Lines, Date, Reference, Tags #1 Address: Street, Number, City #2 Line: Product, Quantity, Price
Objects (JSON with // comments: a type name comes from a type id, a name with ~ is inferred from the schema; dictionary keys that are not strings are not quoted): { // Invoice~ "Id": 1234, "Customer": "Alice", "Billing": { "Street": "Main street", "Number": 12, "City": "Amsterdam" }, // Address~ "Lines": [ // 2 items { "Product": "Apples", "Quantity": 3, "Price": 1.25 }, // Line~, Price: decimal { "Product": "Pears", "Quantity": 2, "Price": 0.99 } // Line~, Price: decimal ], "Date": "2026-10-05T12:30:00Z", // timestamp "Reference": "5bad8f0fcbd99f46a16570867728950e", // bin, 16 bytes, as Guid 0f8fad5b-d9cb-469f-a165-70867728950e "Tags": ["fruit", "fresh"] // 2 items }
It reads any MsgPack, not only data written by LsMsgPack. Errors come with their offset, and the values read after an error are marked.
Requires the .NET runtime 8 or later.
dotnet tool install -g LsMsgPack.Mcp # the command is lsmsgpack-mcp
From source: dotnet publish LsMsgPackMcpServer -c Release -o , then run dotnet /LsMsgPackMcp.dll in place of lsmsgpack-mcp.
| Client | How |
|---|---|
| VS Code (Copilot agent mode) | Nothing to do with the MsgPack Explorer extension: it registers the server "MsgPack (LsMsgPack)". |
| Claude Code | claude mcp add lsmsgpack -- lsmsgpack-mcp |
| Visual Studio 2022 (17.14+) | %USERPROFILE%\.mcp.json (or .mcp.json next to the solution): { "servers": { "lsmsgpack": { "type": "stdio", "command": "lsmsgpack-mcp" } } } |
| Claude Desktop, Cursor, Windsurf... | { "mcpServers": { "lsmsgpack": { "command": "lsmsgpack-mcp" } } } |
In VS Code, MsgPack: Copy MCP Server Configuration... copies these: for the tool when it is installed, otherwise for the server that comes with the extension (its path has the extension's version in it, so copy it again after an update).
| Tool | What it does |
|---|---|
msgpack_debug_status | The IDEs with the MsgPack extension, their debug sessions, and where the program is paused. |
msgpack_debug_locals | The variables of the paused stack frame with their types. The ones that can hold bytes are marked. |
msgpack_debug_read | Reads the bytes of an expression in the paused program and decodes them. Reads byte[], streams (seekable ones go back to their position), Memory , List , HttpContent and base64 or hex strings. In VS Code also JavaScript Uint8Array/Buffer and Python bytes. schemaStore reads the schema from the program's SchemaStore when the payload refers to one. saveTo also writes the bytes to a file. |
msgpack_decode | Decodes data (hex, base64 or byte values), a file, or a doc decoded before. schemas takes a SchemaStore.Export (or one schema) for schema references. |
msgpack_read_as_class | Reads the data into a class of a compiled .NET assembly (assembly: the .dll of the build output, type: the class) and reports what doesn't match: properties the class doesn't have (with "did you mean"), values that don't convert, classes without a schema entry, type ids that aren't found, with the paths of the objects (reporting differences). Also shows the object that was read. The assembly is loaded in a separate process: it runs the class's constructors and setters. |
msgpack_explain_offset | What the byte at an offset is: the items holding it, the object member, the header and content bytes, and the bytes around it. |
msgpack_search | The items holding a text or a value, with offsets and object paths. |
Every decoded payload gets a document id (doc1, doc2...) for follow-up calls. The output can be narrowed and switched with these options:
view: objects (default), items (the MsgPack encodings with offsets) or both.path (e.g. Lines[2]), from/to (a byte range), maxNodes, maxString.offsets adds the offset of every value. issues takes errors, all or none.endian and continueOnError (on by default).The MsgPack extensions of VS Code (MsgPack Explorer) and Visual Studio (MsgPack Debugger Extension) listen on 127.0.0.1. They write a lock file with their port and a random token to ~/.lsmsgpack/ide (%USERPROFILE%\.lsmsgpack\ide). The MCP server uses the IDE that started it, otherwise the one whose workspace holds its working directory (ide picks one when several run).
buffer, this._payload, response.Content, items[2].Data), no method calls. The IDE setting can allow any expression: lsmsgpack.mcp.allowAnyExpression in VS Code (user settings only), Tools > Options > MsgPack Explorer in Visual Studio.lsmsgpack.mcp.enabled in VS Code, and the same options page in Visual Studio.lsmsgpack-mcp decode payload.msgpack # the objects
lsmsgpack-mcp decode payload.msgpack --view items # the items with offsets and encodings lsmsgpack-mcp decode --data "82 a4 4e 61 6d 65 ..." # bytes as text lsmsgpack-mcp explain payload.msgpack 0x7b # what the byte at 0x7b is lsmsgpack-mcp search payload.msgpack Amsterdam lsmsgpack-mcp read-as payload.msgpack --assembly bin/Debug/net8.0/MyApp.dll --type Order # what doesn't match the class lsmsgpack-mcp debug status | debug locals | debug read
lsmsgpack-mcp --help lists the options. Without arguments it runs the MCP server on stdin/stdout.
More: docs/Mcp.md.