MCP Webdav Server MCP Server

A Model Context Protocol server for WebDAV operations with basic authentication

Local serverstdioGo

What is the MCP Webdav Server MCP server?

MCP Webdav Server MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol server for WebDAV operations with basic authentication.

What you get

A Model Context Protocol (MCP) server that enables CRUD operations on a WebDAV endpoint with basic authentication. This server enables Claude Desktop and other MCP clients to interact with WebDAV file systems through natural language commands.

  • Connect to any WebDAV server with optional authentication
  • Perform CRUD operations on files and directories
  • Expose file operations as MCP resources and tools
  • Run via stdio transport (for Claude Desktop integration) or HTTP/SSE transport
  • Secure access with optional basic authentication
  • Support for bcrypt-encrypted passwords for MCP server authentication (WebDAV passwords must be plain text due to protocol limitations)

Setting it up

Installation goes through your MCP client rather than a global install: point it at npx on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once MCP Webdav Server is connected, these are the calls the assistant has available:

  • webdav_create_remote_file — Create a new file on a remote WebDAV server
  • webdav_get_remote_file — Retrieve content from a file stored on a remote WebDAV server
  • webdav_update_remote_file — Update an existing file on a remote WebDAV server
  • webdav_delete_remote_item — Delete a file or directory from a remote WebDAV server
  • webdav_create_remote_directory — Create a new directory on a remote WebDAV server
  • webdav_move_remote_item — Move or rename a file/directory on a remote WebDAV server
  • webdav_copy_remote_item — Copy a file/directory to a new location on a remote WebDAV server
  • webdav_list_remote_directory — List files and directories on a remote WebDAV server

Configuration and credentials

You will need 5 environment variables: WEBDAV_ROOT_URL, WEBDAV_ROOT_PATH, WEBDAV_USERNAME, WEBDAV_PASSWORD, WEBDAV_AUTH_ENABLED. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js 18 or later - npm or yarn - WebDAV server (for actual file operations)

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp webdav server mcp server does with a few real requests.

Choosing this one

This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Webdav Server's toolset — webdav_create_remote_file, webdav_get_remote_file, webdav_update_remote_file and 5 more — is a fair guide to whether it matches your workflow. It is maintained by LaubPlusCo; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Webdav Server's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
webdav_create_remote_fileCreate a new file on a remote WebDAV server
webdav_get_remote_fileRetrieve content from a file stored on a remote WebDAV server
webdav_update_remote_fileUpdate an existing file on a remote WebDAV server
webdav_delete_remote_itemDelete a file or directory from a remote WebDAV server
webdav_create_remote_directoryCreate a new directory on a remote WebDAV server
webdav_move_remote_itemMove or rename a file/directory on a remote WebDAV server
webdav_copy_remote_itemCopy a file/directory to a new location on a remote WebDAV server
webdav_list_remote_directoryList files and directories on a remote WebDAV server

How to install the MCP Webdav Server MCP server

{
  "mcpServers": {
    "webdav-server": {
      "command": "npx",
      "args": ["-y", "npx"],
      "env": {
        "WEBDAV_ROOT_URL": "your-value",
        "WEBDAV_ROOT_PATH": "your-value",
        "WEBDAV_USERNAME": "your-value",
        "WEBDAV_PASSWORD": "your-value",
        "WEBDAV_AUTH_ENABLED": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 18 or later - npm or yarn - WebDAV server (for actual file operations)
VariableDescriptionRequired
WEBDAV_ROOT_URLEndpoint or connection string the server talks to.Yes
WEBDAV_ROOT_PATHFilesystem location the server is allowed to use.Optional
WEBDAV_USERNAMEConfiguration value read at startup.Optional
WEBDAV_PASSWORDConfiguration value read at startup.Optional
WEBDAV_AUTH_ENABLEDConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP Webdav Server to webdav create remote file.
  • Use MCP Webdav Server to webdav get remote file.
  • Use MCP Webdav Server to webdav update remote file.

Frequently asked questions

It connects MCP Webdav Server to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (webdav_create_remote_file, webdav_get_remote_file, webdav_update_remote_file, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Webdav Server directly.