Puter MCP
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
Read ACPI tables from a live QEMU guest or files and explain them for OS developers.
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Python (uv)
SettingsDeveloperEdit Config
{
"mcpServers": {
"acpi": {
"command": "uvx",
"args": [
"acpi-mcp"
]
}
}
}Use Acpi MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Acpi MCP or shows a Acpi MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Acpi MCP yet
Acpi MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Acpi MCP
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
One time only; it works for every server that needs Python (uv)
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user acpi -- uvx acpi-mcpYou should see Acpi MCP listed as connected
Use Acpi MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Acpi MCP or shows a Acpi MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
One time only; it works for every server that needs Python (uv)
Use Acpi MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Acpi MCP or shows a Acpi MCP tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
One time only; it works for every server that needs Python (uv)
Use Acpi MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Acpi MCP or shows a Acpi MCP tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user acpi -- uvx acpi-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"acpi": {
"command": "uvx",
"args": [
"acpi-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"acpi": {
"command": "uvx",
"args": [
"acpi-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"acpi": {
"type": "stdio",
"command": "uvx",
"args": [
"acpi-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026
The registry name was verified with the GitHub account 0xmortuex, which owns the repo
Code last changed 34 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 34 days ago, and the latest version (0.1.0) reached the registry 34 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Puter MCP, XcodeBuildMCP, XcodeBuildMCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Let your AI agent read the firmware's ACPI tables and tell you what they mean.
acpi-mcp is an MCP server that reads ACPI tables and explains them for OS developers. It covers how many CPUs there are and their APIC IDs, where the I/O APIC lives, which ISA IRQs are remapped, where the HPET and PCIe config space are, and the exact port writes that power the machine off or reset it.
It reads tables from three places:
/sys/firmware/acpi/tables, or acpidump -b output from any machine;iasl if you have it installed. Nothing else needs it.Companion to qemu-mcp (boot and drive the VM) and gdbstub-mcp (debug the kernel).
This is real output from QEMU 11 (-M q35 -smp 2), read live from the guest:
> acpi_table MADT
MADT revision 3: local APIC base 0xfee00000 (dual 8259 PICs present: mask them before using the APIC) 2 usable CPU(s), APIC IDs [0, 1] The BSP is usually APIC ID 0; start the others with INIT-SIPI-SIPI I/O APIC id 0 at 0xfec00000, GSI base 0 Interrupt source overrides (legacy ISA IRQ -> GSI): IRQ0 -> GSI 2 (I/O APIC 0 pin 2), bus default, bus default - this is why the PIT timer shows up on I/O APIC pin 2, not 0 IRQ9 -> GSI 9 (I/O APIC 0 pin 9), active high, level - non-ISA polarity/trigger: program the redirection entry to match ... Local APIC NMI on LINT1 for all CPUs (bus default, bus default) - program LVT LINT1 as NMI
acpi_find "how do I shut down the machine?"
Soft power-off (S5): \_S5_ = SLP_TYPa 0, SLP_TYPb 0
acpi_find "reboot"
Reset: write 0xf to I/O port 0xcf9 (8-bit) (FADT RESET_REG, RESET_REG_SUP set). Fall back to the 8042 if it returns.
acpi_find "pci config space"
MCFG: PCI Express ECAM (memory-mapped config space) segment 0, buses 0-255: base 0xb0000000 (256 MiB) config address of bus B, device D, function F, offset O = 0xb0000000 + ((B - 0) << 20 | D << 15 | F << 12 | O)
acpi_table DSDT
8491 bytes of AML bytecode, 37 Device objects Recognised devices: \_SB_.PCI0 PNP0A08 (compatible PNP0A03) PCI Express host bridge \_SB_.HPET PNP0103 HPET \_SB_.PCI0.SF8_.KBD_ PNP0303 PS/2 keyboard (8042) \_SB_.PCI0.SF8_.COM1 PNP0501 16550 serial port (COM) ...
The recipes are tested, not just printed. The integration tests write the exact instructions acpi_find prescribes into a live guest, run them, and check the result: the shutdown recipe powers off both -M pc and -M q35, and the reset recipe resets q35. A control case that only runs hlt keeps running.
ACPI is the first wall every hobby OS hits after "hello world". You need it for SMP, the I/O APIC, the HPET, PCIe and power-off. The tables are binary structures spread across firmware memory, the spec runs to over a thousand pages, and the bugs are silent: miss the IRQ0 → GSI2 override and your timer simply never fires. This server reads the tables your firmware actually built and answers in terms of what to program.
As far as I could find, no other MCP server reads or explains ACPI tables.
pip install acpi-mcp
claude mcp add acpi -- acpi-mcp
Start QEMU with its gdbstub (-s). -S is fine, because acpi-mcp lets the firmware run until the tables exist:
qemu-system-x86_64 -M q35 -smp 2 -kernel kernel.elf -s -S
Then ask your agent something like *"load the ACPI tables from the VM on port 1234 and tell me how to route the keyboard interrupt through the I/O APIC"*.
On a Linux machine you can read its own tables (as root):
acpi_load(name="host", path="/sys/firmware/acpi/tables")
| Tool | What it does |
|---|---|
acpi_load | Load tables under a name from port= (live VM; boot_wait_s lets firmware run first; resume chooses whether the guest runs on afterwards) or from path= (a directory). |
acpi_tables | List every table: address, length, checksum, OEM, and what the table is for. |
acpi_table | Decode one table and explain it: FADT, MADT, HPET, MCFG, DSDT/SSDT, FACS, RSDT/XSDT, WAET, RSDP. |
acpi_interrupt_routing | Map ISA IRQs 0-15 to GSI and I/O APIC pin, with polarity and trigger mode. |
acpi_find | Answer OS-dev questions: shutdown, reset, HPET, PCI config, CPUs, IRQ routing, PM timer, keyboard, serial, RTC century, SCI. |
acpi_dump | Hexdump a table's raw bytes. |
acpi_disassemble | AML to ASL with iasl -d, if installed. |
acpi_sets | List loaded table sets. |
Qqemu.PhyMemMode:1, so ACPI's physical pointers work even when the guest has paging on. On stubs without this packet it reads virtual addresses and says so in the output.0xE0000-0xFFFFF for a checksummed RSD PTR , then walks the XSDT (or RSDT), the FADT, the DSDT and the FACS.-S), it runs the guest in short bursts until a complete, checksum-valid table set exists. It returns as soon as one does.D;1, and the guest continues. Pass resume=False to leave it paused, for example before attaching gdbstub-mcp to a -S VM. QEMU allows only one debugger at a time._STA that hides a device, isn't evaluated. If it ever has to fall back to byte-scanning a region (an If at scope level), the output says so. Use acpi_disassemble (iasl) for an exact listing.acpidump -b) for now.pip install ".[test]" "ruff==0.16.0" "mypy==2.3.0"
ruff check src tests && mypy --strict src pytest tests
The unit tests run on real tables captured from QEMU (tests/fixtures/tables/), so they need no QEMU. tests/test_qemu_integration.py reads live tables from i386 and x86_64 guests on both pc and q35, checks that the CPU count follows -smp, checks resume semantics, and runs the shutdown and reset recipes inside the guest. It skips any QEMU binary that isn't installed.
MIT