Practical overview
When it fits
Use it when an MCP-compatible assistant should interact with a Nextcloud instance through a separately deployed server, rather than using a standalone chat app.
Who it is for
- People who want an external MCP-compatible AI client to work with their Nextcloud data.
- Teams or administrators deploying an MCP server alongside an existing Nextcloud instance.
Documented uses
- Let an AI assistant create, update, search and manage Nextcloud notes.
- Use an assistant to manage calendar events, tasks and availability.
- Give an assistant tools for contacts, files and other supported Nextcloud apps.
- Run a local stdio or Docker-based HTTP MCP service connected to Nextcloud.
Requirements & limits
The repository is public and specifies the AGPL-3.0 license. The README documents local uvx and Docker deployment options.
- An existing Nextcloud instance and an MCP-compatible client are central prerequisites.
- The documented single-user setup uses a Nextcloud app-specific password with Basic Auth.
- The README lists 110+ MCP tools and support across Nextcloud apps, including Mail, Talk, Collectives and Shopping List.
- Semantic search is optional and experimental, and requires Qdrant and Ollama.
- Deployment options include stdio and streamable HTTP transports, with Docker, Kubernetes, VM and local installations listed.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure a local stdio connection
Run the server through uvx and provide its Nextcloud connection details in an MCP client configuration.
Before you start
- A Nextcloud instance
- An MCP client that supports stdio
- uvx
- The Nextcloud host, username and an app-specific password
Steps
Set the Nextcloud host, username and app-specific password as the NEXTCLOUD_HOST, NEXTCLOUD_USERNAME and NEXTCLOUD_PASSWORD environment variables.
Run
uvx nextcloud-mcp-server run --transport stdio, or add the documented command and environment variables to the MCP client's server configuration.
Expected outcome
The MCP client is configured to start the server locally and connect it to the specified Nextcloud instance.
Guide limitations
- This documents setup, not a verified connection or successful operation.
- The guide covers the single-user Basic Auth configuration.
Set up the Docker HTTP connection
Start the server in Docker and configure an MCP client to use its local HTTP endpoint.
Before you start
- Docker
- A Nextcloud instance
- An MCP client that can connect to an HTTP MCP endpoint
- The Nextcloud host, username and an app-specific password
Steps
Provide the Nextcloud host, username and app-specific password as the documented Docker environment variables.
Run the documented container with port 8000 bound to 127.0.0.1.
Configure the MCP client to connect to
http://127.0.0.1:8000/mcp.
Expected outcome
The client is configured to reach the containerized server over the documented local HTTP endpoint.
Guide limitations
- This documents configuration rather than verified operation.
- Semantic search requires additional Qdrant and Ollama infrastructure and is described as experimental.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- cbcoutinho/nextcloud-mcp-server · Official homepage title · retained in its source language