Tetherplane
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Tetherplane — open-source MCP server for authorized AI computer use
Tetherplane is a self-hostable Model Context Protocol (MCP) control plane that connects AI agents to computers their owners explicitly authorize. Its six-tool MCP interface supports files and search, terminal processes, browser automation, Windows desktop operations, and batching — locally or through an authenticated remote relay.
Built for human coexistence: Tetherplane prioritizes background operations and semantic automation instead of taking over a person's browser, keyboard, or cursor. The local agent enforces device and capability policy; the AI client and remote relay cannot override a local denial.
Release status: The historical
v0.1.0GitHub release exists, but the latest Windows three-step onboarding candidate (PR #135) is unsigned and still awaiting independent clean-device acceptance. Do not disable Windows security protections to run it. This README is not a declaration of general-availability readiness.
Start here: What is Tetherplane? · Developer setup · Security policy · Self-hosted remote mode · Acceptance requirements
Default AI-facing surface
Compact MCP exposes exactly six tools:
device
files
process
browser
desktop
batch
Operations are selected with an op field rather than exposing dozens of model-visible tools.
Related MCP server: relaybridge
Architecture
Tetherplane keeps these boundaries separate:
Capability Kernel — canonical invocation/result protocol, policy, response budgets, handles, ownership.
Providers — filesystem/search/process/browser/desktop implementations.
Adapters — Compact MCP, model-neutral JSONL client, RDC compatibility.
Transport — local stdio and optional relay/WebSocket routing.
Policy Broker — local principal grants, allowed roots, approval classes, human-coexistence rules.
The browser and Windows desktop implementations prefer semantic control before physical control. Human-owned resources are protected by default.
Local quick start
Development requires the Rust toolchain from rust-toolchain.toml, Node.js 22+, and pnpm 10.
Build and test with:
corepack enable
corepack prepare pnpm@10 --activate
pnpm install --frozen-lockfile
cargo test --workspace
pnpm -r typecheck
pnpm -r test
pnpm -r buildStart the Compact MCP edge from the repository after building:
node adapters/compact-mcp/dist/stdio-server.js --tetherd target/debug/tetherd.exe --allow C:\path\you\explicitly\allowWindows release package
Build a runtime package:
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/package-windows.ps1 -OutputPath .\dist\Tetherplane-Windows-x64Install per-user into an explicit prefix:
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/install-windows.ps1 -PackagePath .\dist\Tetherplane-Windows-x64 -InstallPrefix "$env:LOCALAPPDATA\Programs\Tetherplane" -StateDir "$env:LOCALAPPDATA\Tetherplane\state"Ordinary uninstall removes installed binaries but preserves state. State purge requires the explicit -PurgeState switch and is only allowed for state created by the installer.
The Windows Compact MCP edge requires a system Node.js runtime. Runtime package dependencies are staged with the release package; pnpm is not required at runtime.
Historical v0.1.0 publication is not evidence that newer developer-beta packages are release-ready. Before any new public release, complete the operator-observed acceptance requirements in docs/live-acceptance.md, including local filesystem/process/browser/desktop proof and authenticated remote verification without human disruption.
Remote mode
tether-relay provides pairing, account/device routing, Streamable HTTP MCP, outbound device WebSockets, revocation, and reconnect isolation. Production direct relay transport requires HTTPS/WSS. Plain HTTP/WS is restricted to explicit loopback development mode.
See docs/remote/self-host.md and docs/security/remote-plane.md.
Browser and desktop coexistence
Browser automation uses extension-first authenticated-profile operation with isolated CDP fallback. Human-owned tabs are not navigated or closed in background mode.
Windows desktop automation uses UI Automation semantic patterns. Invoke, Value, Selection, Toggle, Expand, and Collapse do not require physical pointer movement. Physical fallback is isolated behind scoped, expiring ForegroundLeases and recent human activity can block it.
See docs/security/threat-model.md and docs/recovery.md.
Compatibility
A separate RDC-shaped compatibility endpoint maps legacy core workflows to canonical Tetherplane semantics without changing the six-tool Compact MCP interface. See docs/compatibility/rdc.md.
Measured performance
Measured values are published under docs/benchmarks/. They are evidence from named machines, not marketing claims.
The original Leno baseline met the idle-memory target but missed the original cold-start target. That historical miss is retained honestly. The fresh Plan F release-candidate measurement at canonical commit c1ea567c09fe2a0244ff12db2864cf309e0fedaf recorded a 256.95 ms cold start, 12.21 MiB idle working set, and the exact six-tool surface. The original <250 ms cold-start target therefore remains a narrow measured miss in this run. See docs/benchmarks/release-candidate-2026-09-21.md.
Security
Do not put credentials, bearer tokens, browser cookies, or device secrets in Git history, command output, fixtures, or logs. See SECURITY.md and docs/security/threat-model.md.
Contributing
See CONTRIBUTING.md. Tetherplane development uses written plans for multi-step work, strict TDD for implementation, systematic root-cause debugging, and fresh verification before completion claims.
License
Licensed under either Apache License 2.0 (LICENSE-APACHE) or MIT (LICENSE-MIT), at your option.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Remote MCP for Copilot CLI switch gate MCP, structured receipts, audit logs, and reviewer-ready evid
MCP-first control plane for ProAgentStore agents and private instances.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceOpen-source, Windows-first control plane for operating local and homelab services through typed MCP servers, featuring 13 servers and 290 tools with infrastructure adapters for Windows, Ubuntu, Docker, and more.2MIT
- AlicenseNot gradedqualityBmaintenanceProvides a local Windows control plane for PowerShell and AI CLIs, exposing MCP tools for safe terminal sessions, bounded provider calls, routing, committees, and run receipts.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceA custom MCP server for orchestrating Windows/Linux/macOS workstations, providing filesystem, shell, SSH, and personal productivity tools with security features like allowlisting and human-in-the-loop approval for writes.MIT
- AlicenseNot gradedqualityBmaintenanceOpen-source Windows MCP policy gateway that gives ChatGPT controlled access to local files and terminal sessions with workspace-scoped permissions, guarded writes, session-owned processes, and audit logging.5Apache 2.0