Scripthold MCP Server

Scripthold — Secure MCP Server for Local Workspaces

Code from the web. Work locally. Recover safely.

Scripthold is a Model Context Protocol (MCP) server that gives web, desktop, and CLI agents controlled access to explicitly authorized local workspaces. It safely handles legacy text encodings, deterministic file changes, source navigation, backups, and optional durable local execution over stdio or authenticated Streamable HTTP.

AI clients see Настройки — not ???? or Íàñòðîéêè.

What Scripthold provides

The current public release is Scripthold 3.2.1 with 38 tools and 3 guided prompts.

• 168 registered text encodings with content-based detection, UTF-32 LE/BE support, and conservative ambiguity handling.
• 101 active Source Intelligence providers for bounded declaration navigation, structural search, selected project relations, and verified context assembly.
• Secure workspace boundaries with canonical-root containment, Windows reparse/junction handling, deterministic traversal, and missing-path validation.
• Approval-bound mutations using preview/apply capabilities, exact fingerprints, conflict checks, staged writes, and truthful partial-state reporting.
• Optional persistent backups with history, compare, audit, restore, explicit garbage collection, pinning, and exact-ID deletion.
• Durable asynchronous tasks with idempotency, persistent state, bounded logs, recovery, locks, and cancellation.
• Reliable long-running read-only calls through optional deferred-operation storage and bounded retained-result retrieval.
• Authenticated Streamable HTTP with loopback defaults, bearer authentication, Host/Origin validation, resource limits, and explicit TLS/proxy requirements for non-loopback exposure.

Scripthold originated from the original mcp-file-tools project, created by Dimitar Grigorov, and retains its GPL-3.0 lineage. See Project Direction.

Quick start

Use a published release

Download the asset for your platform from the latest release and verify it against checksums.txt. Releases also attach a signed Sigstore build-provenance bundle for the normal GoReleaser assets.

Build from source

git clone https://github.com/zoster81/scripthold.git
cd scripthold
go test ./...
go build -o scripthold ./cmd/scripthold

The module path is github.com/zoster81/scripthold.

Local stdio client

Pass each authorized directory as a startup argument:

{
  "mcpServers": {
    "scripthold": {
      "type": "stdio",
      "command": "C:\\Tools\\scripthold_windows_amd64.exe",
      "args": ["D:\\Projects"]
    }
  }
}

Startup roots are authoritative. A roots-capable stdio client may supply dynamic roots only when the process starts without directory arguments.

Streamable HTTP

HTTP requires exactly one bearer-token source. A minimal loopback PowerShell launch is:

$tokenPath = Join-Path $env:TEMP "scripthold.token"
$bytes = New-Object byte[] 32
$rng = [System.Security.Cryptography.RandomNumberGenerator]::Create()
try { $rng.GetBytes($bytes) } finally { $rng.Dispose() }
[System.IO.File]::WriteAllText($tokenPath, [Convert]::ToBase64String($bytes), [System.Text.UTF8Encoding]::new($false))

$env:MCP_HTTP_TOKEN_FILE = $tokenPath
$env:MCP_HTTP_ADDR = "127.0.0.1:8765"
.\scripthold_windows_amd64.exe --transport=streamable-http D:\Projects

The MCP endpoint is http://127.0.0.1:8765/mcp; /healthz and /readyz expose liveness/readiness. Send the token as Authorization: Bearer <token> on every MCP request.

Do not expose HTTP beyond loopback without reading HTTP Security. Non-loopback use requires explicit opt-in and TLS or a trusted proxy boundary.

OpenAI Secure MCP Tunnel

Sanitized PowerShell examples are available under examples/:

• start-local-stdio.ps1
• start-local-http.ps1
• start-openai-tunnel-stdio-plus-local-http.ps1
• start-openai-tunnel-http-plus-local-stdio.ps1

Copy an example outside the checkout before replacing placeholders. Never commit Runtime API keys, Tunnel IDs, bearer tokens, or private state paths.

Container

docker build --build-arg VERSION=dev -t scripthold:dev .

docker run --rm -i \
  --read-only \
  --cap-drop=ALL \
  --security-opt=no-new-privileges \
  --tmpfs /tmp:rw,noexec,nosuid,size=64m \
  --mount type=bind,source=/absolute/project,target=/data \
  scripthold:dev --transport=stdio /data

The image runs as unprivileged UID/GID 10001.

Tool groups

TOOLS.md is the detailed public reference for schemas, parameters, examples, limits, and error behavior. The catalog currently includes:

Source Intelligence

Source Intelligence is read-only. It does not execute project code and does not require external parser/compiler/LSP processes.

source_symbols provides bounded outline, digest, find, and fingerprint-bound show. source_query provides structural search, supported project relations, dependency graphs, and fingerprint-verified context. Unsupported or ambiguous relationships fail closed rather than being guessed.

The generated provider/capability matrix is in Language Capabilities.

Safety model

• File access is limited to explicitly authorized roots after canonical path validation.
• Symlink, junction, reparse-point, alias, and missing-path escapes fail closed.
• Encoding detection uses bytes and decoded-content evidence, never filenames or extensions.
• Mutations stage and revalidate before commit; initially missing destinations use no-replace semantics.
• Preview/apply workflows bind the approved operation to a one-shot capability so mutation parameters cannot be changed at apply time.
• Multi-file mutations do not claim transactional rollback; failures report committed/unchanged/unknown state where applicable.
• The optional backup store is a separate protected authority outside public roots.
• task_run execution is disabled by default. Shell and script execution require explicit authorization; HTTP requires an additional HTTP execution opt-in.
• HTTP is authenticated and loopback-only by default.

Current architectural boundaries are summarized in Architecture.

Key configuration

Most installations need only a small subset of environment variables:

Detailed limits and subsystem-specific options are documented where they are used: TOOLS.md, Durable Tasks, and HTTP Security.

Typical uses

• Safely edit legacy source/configuration files without corrupting encoding or line endings.
• Search mixed-encoding repositories with explicit partial-coverage evidence.
• Navigate heterogeneous source trees without loading entire projects into the model.
• Preview and approve exact single- or multi-file changes.
• Keep persistent pre-state backups and restore selected versions.
• Run long builds/tests without tying process lifetime to one MCP request.
• Serve the same workspace toolset through local stdio, authenticated HTTP, containers, or a secure tunnel bridge.

Documentation

• Tool Reference — public MCP tools, schemas, examples, and limits.
• Architecture — current product and security boundaries.
• HTTP Security — HTTP deployment and threat model.
• Durable Tasks — persistent task execution.
• Language Capabilities — generated Source Intelligence matrix.
• Roadmap — current and future work only.
• Migration 2.0 / Migration 3.0 — intentional compatibility changes.
• Contributing / Publishing / Security — maintainer and contributor guidance.
• Changelog — concise release and unreleased user-visible changes.

Development

The required Go version is declared by go.mod.

go mod verify
go test ./...
golangci-lint run ./...
go build -o scripthold ./cmd/scripthold

See CONTRIBUTING.md before proposing changes.

License

GPL-3.0 — see LICENSE.