WebDAV MCP

io.github.vernonstinebakerPublished by GitHub account vernonstinebakerv1.1.1Updated Oct 24, 2026

Zero-dependency WebDAV MCP server — single static binary, no Node.js or Python. 8 tools via stdio.

VerifiedSTDIODesktop onlyCloud & InfrastructureFiles & Storage

Overview

AI-generated overview

A zero-dependency WebDAV MCP server, shipped as a single static binary, that lets an assistant list, read, write, move, copy and delete files on a WebDAV server

What you can do
List files and directories at a path, optionally recursively, and get metadata (size, modified time, etag, type) for a single file or directory via stat. Read file contents as text with a configurable maximum size. Write, create or overwrite files with a chosen MIME type, optionally creating missing parent directories. Create directories, move or rename files and directories, copy files and directories, and delete files or directories.
When to use it
Useful when an assistant needs to work with files on an existing WebDAV server, such as a self-hosted NAS, Nextcloud-style share or internal file service, without installing a Node.js or Python runtime. Suited to desktop setups where a small static binary is preferred.
Requirements
Runs as a local process over stdio on desktop platforms; prebuilt binaries are provided for macOS (Apple Silicon and Intel) and Linux (x86-64, ARM64, ARMv7). Needs a reachable WebDAV server and the environment variables WEBDAV_URL (required), WEBDAV_USER and WEBDAV_PASS. Building from source requires Zig 0.16.0.
Before you install
The server holds WebDAV credentials in WEBDAV_PASS and sends them with HTTP Basic authentication, so use HTTPS or a trusted network. Tools can write, overwrite, move, copy and delete files and directories on the remote server, including recursive operations; review destructive calls before allowing them. Recursive listing may be blocked by some servers.

Installation

In SourceWeft

  1. Open WebDAV MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

webdav-mcp

A zero-dependency WebDAV MCP server — single static binary, no Node.js or Python required.

Implements the Model Context Protocol (MCP) over JSON-RPC 2.0 via stdio, exposing 8 WebDAV operations as tools that any MCP-compatible AI agent can call.

Why this exists

Every other WebDAV MCP server on GitHub requires a Node.js or Python runtime. This one is a single self-contained binary (~100–160 KB) compiled from Zig. It runs anywhere without installing a runtime, and it cross-compiles to all major platforms from one machine.

Tools

ToolDescription
listList files and directories at a path
readRead file contents as text
writeWrite (create or overwrite) a file
deleteDelete a file or directory
mkdirCreate a directory
moveMove or rename a file or directory
copyCopy a file or directory (sends Depth: infinity per RFC 4918 §9.8.2)
statGet metadata for a single file or directory (PROPFIND Depth:0)

Tool parameters

list

  • path (required) — directory path relative to WebDAV root
  • recursive (boolean, default false) — if true, lists recursively using Depth: infinity. Note: some servers (IIS, some nginx configs) block recursive listing.

read

  • path (required) — file path relative to WebDAV root
  • max_bytes (integer, default 1048576) — maximum file size to read in bytes. Returns an error if the file is larger. Increase this for large files.

write

  • path (required) — file path relative to WebDAV root
  • content (required) — content to write
  • content_type (string, default application/octet-stream) — MIME type for the file (e.g. text/plain, application/json)
  • create_parents (boolean, default false) — if true and the parent directory does not exist, automatically creates all missing ancestor directories via MKCOL before writing

stat

  • path (required) — path to stat relative to WebDAV root
  • Returns: file or dir or missing, plus size=, modified=, etag=, and type= when available

Configuration

Set these environment variables before launching the server:

VariableDescriptionExample
WEBDAV_URLBase URL of the WebDAV serverhttp://192.168.1.10:8080
WEBDAV_USERUsernameadmin
WEBDAV_PASSPasswordsecret

Credential security

Credentials are sent via native Zig HTTP networking using the Authorization: Basic ... header. No external curl process is spawned.

Building from source

Requires Zig 0.16.0.

bash
# Development buildzig build
# Optimized release build (~100-160 KB)zig build -Doptimize=ReleaseSmall
# Cross-compile for all platforms (outputs to zig-out/release/)zig build cross

Cross-compilation targets

FilePlatform
webdav-mcp-macos-arm64macOS Apple Silicon
webdav-mcp-macos-x86_64macOS Intel
webdav-mcp-linux-arm64Linux ARM64 (static musl)
webdav-mcp-linux-x86_64Linux x86-64 (static musl)
webdav-mcp-linux-armv7Linux ARMv7 / Raspberry Pi (static musl)
webdav-mcp-windows-x86_64.exeWindows x86-64

Integration with nullclaw / *Claw bots

Add an mcp_servers entry to your bot's config.json:

json
{  "mcp_servers": {    "webdav": {      "command": "/path/to/webdav-mcp",      "args": [],      "env": {        "WEBDAV_URL": "http://your-webdav-server:8080",        "WEBDAV_USER": "your-username",        "WEBDAV_PASS": "your-password"      }    }  }}

The server speaks JSON-RPC 2.0 over stdio (newline-delimited), which is the standard MCP transport. Once registered, the agent can call all 8 tools as normal tool calls.

Running tests

bash
zig build test --summary all

All unit tests cover XML parsing, JSON-RPC dispatch, argument extraction, URL construction, percent-encoding, entity decoding, and HTTP method routing.

License

MIT — see LICENSE.

Source: README.md at commit fd45113

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts