WebDAV MCP

WebDAV MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/vernonstinebaker/webdav-mcp/releases/download/v1.1.1/webdav-mcp-macos-arm64. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client. It reads these environment variables: WEBDAV_URL (required), WEBDAV_USER and WEBDAV_PASS (secret); set them in the client's configuration for this server.

WebDAV MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/vernonstinebaker/webdav-mcp/releases/download/v1.1.1/webdav-mcp-macos-x86_64. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client. It reads these environment variables: WEBDAV_URL (required), WEBDAV_USER and WEBDAV_PASS (secret); set them in the client's configuration for this server.

WebDAV MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/vernonstinebaker/webdav-mcp/releases/download/v1.1.1/webdav-mcp-linux-x86_64. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client. It reads these environment variables: WEBDAV_URL (required), WEBDAV_USER and WEBDAV_PASS (secret); set them in the client's configuration for this server.

WebDAV MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/vernonstinebaker/webdav-mcp/releases/download/v1.1.1/webdav-mcp-linux-arm64. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client. It reads these environment variables: WEBDAV_URL (required), WEBDAV_USER and WEBDAV_PASS (secret); set them in the client's configuration for this server.

WebDAV MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/vernonstinebaker/webdav-mcp/releases/download/v1.1.1/webdav-mcp-linux-armv7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client. It reads these environment variables: WEBDAV_URL (required), WEBDAV_USER and WEBDAV_PASS (secret); set them in the client's configuration for this server.

WebDAV MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/vernonstinebaker/webdav-mcp/releases/download/v1.1.1/webdav-mcp-windows-x86_64.exe. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client. It reads these environment variables: WEBDAV_URL (required), WEBDAV_USER and WEBDAV_PASS (secret); set them in the client's configuration for this server.

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect