Sonicake Pocket Master

Name: Sonicake Pocket Master
Author: voronkovd

作者：voronkovd版本 0.1.0i★ –i在你的电脑上运行

注册名称io.github.voronkovd/pocket-master-mcp

安装

概览

作者提供的说明（英文原文）

Control a Sonicake Pocket Master guitar processor over USB MIDI: amps, effects and presets.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： PM_PORT, PM_DATA_DIR, PM_DEBUG_TOOLS

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "pocket-master": {
      "command": "uvx",
      "args": [
        "pocket-master-mcp"
      ],
      "env": {
        "PM_PORT": "your-value",
        "PM_DATA_DIR": "your-value",
        "PM_DEBUG_TOOLS": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add pocket-master --env PM_PORT=your-value --env PM_DATA_DIR=your-value --env PM_DEBUG_TOOLS=your-value -- uvx pocket-master-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "pocket-master": {
      "command": "uvx",
      "args": [
        "pocket-master-mcp"
      ],
      "env": {
        "PM_PORT": "your-value",
        "PM_DATA_DIR": "your-value",
        "PM_DEBUG_TOOLS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "pocket-master": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "pocket-master-mcp"
      ],
      "env": {
        "PM_PORT": "your-value",
        "PM_DATA_DIR": "your-value",
        "PM_DEBUG_TOOLS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

PM_PORT env
Substring of the MIDI port name (default: auto-detect)
PM_DATA_DIR env
Where backups, tone files, language packs and logs are stored (default ~/.pocket-master-mcp)
PM_DEBUG_TOOLS env
1 exposes low-level research tools

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 voronkovd 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18352 个服务器的 0%
发布到注册中心的时间比此分类中其他 18352 个服务器的 56% 更新
基础检查结果等于或优于此分类中其他 18352 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Sonicake Pocket Master 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.0）于35天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Hunter Killer

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

Hunter Killer

作者：Irishman-Management-LLC

Liquidation walls, snapshot age, evidence labels and a public record. Managed OAuth.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

pocket-master-mcp

An MCP server that lets an AI assistant (Claude Desktop or any other MCP client) control a Sonicake Pocket Master guitar processor over USB MIDI. It also includes offline tools that translate the device's UI into other languages, with Russian built in.

Describe the sound you want in plain words ("tight modern metal rhythm", "clean with a wide chorus, less reverb"). The assistant picks models, sets parameters, reorders the chain, and saves and names presets on the unit.

Unofficial project. It is not affiliated with or endorsed by Sonicake. The protocol is based on the reverse-engineering work in PocketEdit. Reading (current preset, preset names, the full edit buffer) is verified on a real unit with firmware V1.3.3. Writing presets has seen little hardware testing so far, so run `backup_presets` first. Patched firmware is unofficial too: you use it at your own risk.

What it can do

Live editing: select a model in any block (22 amps + 5 captured-amp profiles, 20 cabs/IRs, 8 drives, FX1/FX2 with 15–17 effects each, 9 delays, 10 reverbs, 3 EQs, noise gate), switch blocks on and off, and set parameters by name with range checking (Gain, Time in ms, Rate in Hz, Mode = Bass, +3dB = on, …).
Signal chain: reorder NR / FX1 / FX2 / DLY / RVB around the fixed DRV-AMP-IR-EQ block.
Read state: decode the edit buffer (models, on/off, parameter values, chain, preset volume) and list the 100 preset names.
Presets: select presets, save the edit buffer to a user slot P01–P50 with a name, rename presets, back up and restore presets.
Tone files: apply a whole tone from a JSON file. Examples are in examples/presets.
Globals: global volume, input / FX rec / monitor / BT rec levels.
UI language: build a firmware file with a translated UI (Russian built in, see UI language).

Requirements

A Sonicake Pocket Master connected over USB. It shows up as a class-compliant MIDI port.
Python 3.10+.
An MCP client, for example Claude Desktop.

The server has to run on the computer the Pocket Master is plugged into, because it needs direct access to the USB MIDI port.

Installation

The easiest way is uv: uvx downloads and runs the server.

Claude Desktop

Open Settings → Developer → Edit Config and add:

"mcpServers": { "pocket-master": { "command": "uvx", "args": ["pocket-master-mcp"] } } }

Restart Claude Desktop completely. If Claude cannot find uvx, use its absolute path (which uvx, typically ~/.local/bin/uvx). For firmware previews (PNG), use "args": ["--from", "pocket-master-mcp[preview]", "pocket-master-mcp"].

Alternatively, run pipx install pocket-master-mcp or pip install "pocket-master-mcp[preview]" and use "command": "pocket-master-mcp".

From source

git clone https://github.com/voronkovd/pocket-master-mcp.git

cd pocket-master-mcp python3 -m venv .venv .venv/bin/pip install -e ".[dev]"

Then use "command": "/absolute/path/to/pocket-master-mcp/.venv/bin/pocket-master-mcp".

Configuration

Variable	Default	Meaning
`PM_PORT`	auto	substring of the MIDI port name. Without it, the server looks for "Pocket", "Sonicake", "QME" and otherwise probes every port.
`PM_DATA_DIR`	`~/.pocket-master-mcp`	where backups, tone files, language packs and logs are stored
`PM_DEVICE_MAP`	bundled	path to a custom `device_map.json`
`PM_DEBUG_TOOLS`	off	`1` exposes `debug_send`, `debug_monitor` and `debug_raw_dump`

Checking the connection

From a source checkout, run python scripts/midi_check.py. It is read-only: it prints the ports, the current preset and the preset names.
In Claude: *"connect to the Pocket Master and show the device state"*. Compare the models and values with the screen of the unit.
If something is decoded wrongly, set PM_DEBUG_TOOLS=1 and ask for debug_raw_dump. It writes the raw dump with offsets to ~/.pocket-master-mcp/logs/. Please attach it to an issue.

Tools

Tool	What it does
`connect`, `list_midi_ports`	find and open the Pocket Master
`device_state`	edit buffer: preset, chain, amp mode, models, on/off, parameter values
`list_models(block)`	models of a block with their parameters and ranges
`set_model(block, model, on)`	select a model by name
`set_block(block, on)`	switch a block on or off
`set_param(block, param, value)`	set a parameter of the current model
`set_chain(order)`	signal chain order
`set_preset_volume`, `set_global`	preset volume, global settings
`apply_preset(spec)`	apply a whole tone in one call
`list_presets`, `select_preset`	preset names, load a preset
`save_preset(preset, name)`	save the edit buffer to P01–P50, verified by reading the names back
`rename_preset`	rename a user preset
`backup_presets`, `list_backups`, `restore_preset`	backups as JSON
`save_preset_file`, `list_preset_files`, `load_preset_file`	tone files
`list_user_slots`	names of the user IRs and captured-amp profiles
`firmware_info`, `firmware_strings`	inspect a firmware `.bin`: version, sections, CRCs, UI strings
`list_language_packs`, `get_language_pack`, `save_language_pack`	UI translations (English string → translation)
`build_language_firmware`	build a firmware with the second UI language replaced by a language pack, plus a PNG preview
`preview_firmware_strings`	render a firmware's UI strings with its own font

Blocks are nr (gate), fx1, drv, amp, ir, eq, fx2, dly, rvb. Aliases such as gate, drive, cab, delay and reverb also work. Captured-amp profiles (User Profile 1..5) are selected in the amp block, and the server switches the amp mode automatically.

UI language (firmware)

The firmware has two UI languages, English and Chinese. build_language_firmware replaces the Chinese one with a language pack: Russian (ru) is built in, and your own packs can be saved with save_language_pack. It works offline on a copy of the official firmware file, never on the device. Flash the result with the official Sonicake Manager, then choose the language in the device's settings. To go back, flash the official file.

A pack maps English UI strings to translations. Strings that are not listed stay English. Effect and parameter names exist only in English in the firmware and are not translated.
The device font is a tiny pixel font, so glyphs are hand-drawn in data/glyphs.json. Cyrillic is included. For other scripts, add glyphs there first; the build stops and lists any character without a glyph.
The build checks the result: CRCs, every string, a glyph for every character, and that only the UI section changed. It refuses already-patched input, and it never overwrites the source.
This is unofficial, so use it at your own risk. It was tested on V1.3.3 and builds for V1.1.0. Details are in docs/FIRMWARE.md.

Example: *"Build a Russian firmware from ~/Downloads/Pocket Master Firmware V1.3.3.bin, but use 'Сохр.' for Save."*

The same is available without an MCP client:

pocket-master-fw info  "Pocket Master Firmware V1.3.3.bin"

pocket-master-fw build "Pocket Master Firmware V1.3.3.bin" -l ru --set "Save=Сохр."

Firmware files are not part of this project. Download them from Sonicake.

Tone format

"chain": ["nr", "fx1", "drv", "amp", "ir", "eq", "fx2", "dly", "rvb"], "blocks": { "drv": {"model": "Scream", "params": {"Gain": 5, "Tone": 60, "Vol": 85}}, "amp": {"model": "Sol 100 LD", "params": {"Gain": 62, "Middle": 58}}, "ir": {"model": "BritGN 4x12"}, "dly": {"on": false}, "rvb": {"model": "Room", "params": {"Mix": 10}} }, "preset_volume": 70 }

Selecting a model resets its parameters to the model defaults, so parameters are applied after the model (apply_preset does this in the right order).

Limitations

Only the edit buffer can be dumped. Backups therefore load every preset one by one, and unsaved edits are lost.
Backups store decoded settings, not raw preset bytes, so anything the decoder does not know (if anything) is not restored.
Global settings can be written but not read yet.
User IR / captured-amp *contents* cannot be uploaded, only selected.

How it works

docs/PROTOCOL.md: MIDI SysEx framing (nibble expansion, CRC-8), commands, the edit-buffer dump and the preset names.
docs/FIRMWARE.md: the HTFW firmware container, the update protocol of Sonicake Manager, and the LVGL UI fonts and string tables.
tools/build_device_map.py regenerates the model and parameter table from a PocketEdit checkout.

Development

.venv/bin/pip install -e ".[dev]"

.venv/bin/pytest

The tests rebuild a sample of the device commands captured by PocketEdit and real replies from a unit, and they run the device logic against a fake Pocket Master, so no hardware is needed. Firmware build tests run when an official firmware file is in local/ or PM_TEST_FIRMWARE points to one.

Credits and license

PocketEdit by suckyble and contributors (hnikolov and others) is the source of the protocol knowledge. The model and parameter table (data/device_map.json, regenerated by tools/build_device_map.py) and the command samples in tests/fixtures/pocketedit_commands.json are derived from its libraries. PocketEdit does not state a license. If you are its author and want these files changed or removed, please open an issue.
The firmware language tools contain no Sonicake code or data. They patch a firmware file the user supplies.

This code is MIT licensed, see LICENSE. Sonicake and Pocket Master are trademarks of their owners. Model names refer to the products they emulate and are used only to identify the models.