Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add pyproc -- npx -y pyproc@0.0.46รันในเทอร์มินัล
{ "mcpServers": { "pyproc": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
pyproc is a browser computer built around an owned, worker-hosted CPython 3.14 WASI kernel. The npm package includes the verified engine and standard library, so the default runtime does not require a separate engine download or a remote execution service.
A persistent Python computer in the browser: real CPython, durable workspaces, rewindable history, and evidence-backed browser eyes and hands. No application server. (브라우저에 영속하는 Python 컴퓨터.)
npm install pyproc
Serve the installed package from the same origin as your application.
The supported production browser boundary is current Chromium and Edge with SharedArrayBuffer and
cross-origin isolation enabled.
Serve every page that boots pyproc with these headers:
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Embedder-Policy: require-corp
Vite (vite.config.js):
export default {
server: {
headers: {
"Cross-Origin-Opener-Policy": "same-origin",
"Cross-Origin-Embedder-Policy": "require-corp",
},
},
preview: {
headers: {
"Cross-Origin-Opener-Policy": "same-origin",
"Cross-Origin-Embedder-Policy": "require-corp",
},
},
};
Next.js (next.config.js):
module.exports = {
async headers() {
return [{
source: "/:path*",
headers: [
{ key: "Cross-Origin-Opener-Policy", value: "same-origin" },
{ key: "Cross-Origin-Embedder-Policy", value: "require-corp" },
],
}];
},
};
Confirm the installed package and headers on this machine:
npx pyproc-playground
checkEnvironment() reports the same Setup requirements when the page is missing a header or JSPI.
import { boot } from "pyproc";
const machine = await boot();
const receipt = await machine.run.python("print(sum(range(100)))");
console.log(receipt.output); // 4950
await machine.close();
Every execution returns a structured receipt. Python exceptions produce a stable PyProcError with
code === "PYPROC_KERNEL_EXECUTION_ERROR".
Install with the same commands a Python session already uses:
await machine.run.python(`
%pip install pyproc-native-host==1.0.0
import pyproc_native_host
print(pyproc_native_host.ABI_VERSION)
`);
python -m pip install ... is the same door. import is ordinary CPython import. subprocess pip and
arbitrary native wheels are outside this engine: there is no OS process, and WASI cannot load those ABIs.
The package environment is the host contract
behind those Python commands.
import { boot, open } from "pyproc";
const machine = await boot({ deterministic: true });
await machine.run.python("counter = 41");
const image = await machine.history.export();
await machine.close();
const restored = await open(image);
console.log(await restored.run.get("counter")); // 41
await restored.close();
A Machine image carries a verified engine reference and content-addressed checkpoint objects. It does not duplicate the engine binary.
Checkpoint, restore, and export live on machine.history.
Default boot() stays the owned WASI kernel (CPython 3.14.6). When createWebComputer({ linux }) has
a linuxOs guest, the same computer also exposes native Linux CPython over that guest's serial console:
import { createWebComputer } from "pyproc";
const computer = createWebComputer({ linux: { V86, manifest } });
await computer.bootAll();
if (computer.linuxPython.available) {
await computer.linuxPython.run("print(40 + 2)");
await computer.linuxPython.pip(["install", "demo==1.0.0"]);
}
This door does not replace boot(). The guest interpreter is CPython 3.12.13, not the WASI 3.14.6
kernel. The slim Buildroot linux image stays without CPython. The catalog asset
buildroot-pyproc-python-i686.bin is the image that contains python3 and pip 25.2.
linuxPython.pip sends python3 -m pip over serial. The receipt stdout is that serial transcript.
Network indexes and arbitrary wheels are outside the tested door. WASI %pip stays on the owned
catalog and is a different path.
Machine Entrance starts the installed
pyproc-control and MCP path. The API reference
and platform requirements cover the
remaining doors.
Mozilla Public License 2.0. Copyright 2026 eddmpython.
A persistent Python computer in the browser: real CPython, durable workspaces, rewindable history, and evidence-backed browser eyes and hands. No application server. (브라우저에 영속하는 Python 컴퓨터.)
{ "mcpServers": { "pyproc": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Pyproc ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-14 A persistent Python computer in the browser: real CPython, durable workspaces, rewindable history, and evidence-backed browser eyes and hands. No application server. (브라우저에 영속하는 Python 컴퓨터.)