The interface is localized. Skill descriptions and documents are machine-translated by AI into your language; code, commands, paths and technical terms stay in the original, and the author's document governs.
Explore skills
Development · SKILL.md

nextcloud-mcp-connector

nextcloud-mcp-connector

MCP connector for Nextcloud – enables AI-powered file management, collaboration, and app integration through Claude

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill documentation

GitHub

name: nextcloud-mcp-connector description: "MCP connector for Nextcloud – enables AI-powered file management, collaboration, and app integration through Claude" license: AGPL tags: ["cloud","file-management","mcp","nextcloud","collaboration"] difficulty: intermediate time_to_master: "4-8 weeks" version: "1.0.0"

Nextcloud MCP Connector

Overview

This skill enables Claude to interact with Nextcloud through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Nextcloud's WebDAV/OCS API, allowing natural language control of Nextcloud operations, intelligent automation, and AI-powered assistance for Nextcloud workflows.

When to Use This Skill

  • File and folder management via natural language
  • Share and permission configuration
  • Calendar and contact management
  • App installation and configuration
  • User and group administration

Architecture

┌─────────────┐     ┌─────────────────┐     ┌──────────────────┐
│   Claude     │────▶│   MCP Server    │────▶│   Nextcloud        │
│   (Client)   │◀────│   (TypeScript)  │◀────│   (WebDAV/OCS API)│
└─────────────┘     └─────────────────┘     └──────────────────┘

Core Concepts

MCP Server Setup

The connector implements an MCP server that exposes Nextcloud operations as tools Claude can invoke. The server translates natural language intentions into WebDAV/OCS API calls.

Key Endpoints/Interfaces

/remote.php/dav/files, /ocs/v2.php/apps/files_sharing/api/v1, /ocs/v2.php/cloud/users, /ocs/v2.php/apps/notifications

Implementation

// Nextcloud MCP Server Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({
  name: "nextcloud-mcp-connector",
  version: "1.0.0",
});

// Tool: List/Query Resources
server.tool(
  "list_resources",
  "List and query Nextcloud resources with optional filters",
  {
    query: z.string().optional().describe("Search query or filter"),
    limit: z.number().optional().describe("Max results to return"),
  },
  async ({ query, limit }) => {
    // Call Nextcloud WebDAV/OCS API
    const response = await fetch(`${BASE_URL}/remote.php/dav/files`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
    };
  }
);

// Tool: Create Resource
server.tool(
  "create_resource",
  "Create a new resource in Nextcloud",
  {
    name: z.string().describe("Resource name"),
    config: z.object({}).passthrough().optional().describe("Resource configuration"),
  },
  async ({ name, config }) => {
    const response = await fetch(`${BASE_URL}/remote.php/dav/files`, {
      method: "POST",
      headers: {
        "Authorization": `Bearer ${API_KEY}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({ name, ...config }),
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: `Created: ${JSON.stringify(data)}` }],
    };
  }
);

// Tool: Analyze/Report
server.tool(
  "analyze",
  "AI-powered analysis of Nextcloud data",
  {
    type: z.string().describe("Analysis type"),
    timeframe: z.string().optional().describe("Time range for analysis"),
  },
  async ({ type, timeframe }) => {
    // Fetch data and provide AI analysis
    const response = await fetch(`${BASE_URL}/remote.php/dav/files`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
    };
  }
);

// Start server
const transport = new StdioServerTransport();
await server.connect(transport);

Claude Desktop Configuration

{
  "mcpServers": {
    "nextcloud-mcp-connector": {
      "command": "node",
      "args": ["path/to/nextcloud-mcp-connector/index.js"],
      "env": {
        "NEXTCLOUD_API_KEY": "your-api-key",
        "NEXTCLOUD_BASE_URL": "https://your-instance-url"
      }
    }
  }
}

Best Practices

  1. Authentication: Store API keys securely using environment variables; never hardcode credentials
  2. Rate Limiting: Implement request throttling to respect Nextcloud API rate limits
  3. Error Handling: Provide clear, actionable error messages for common failure scenarios
  4. Pagination: Handle paginated responses for large datasets efficiently
  5. Caching: Cache frequently accessed read-only data to reduce API calls
  6. Security: Validate all inputs before passing to the Nextcloud API; sanitize outputs
  7. Logging: Log all API interactions for debugging and audit purposes

Example Prompts

"Share the project folder with the team group with edit permissions and set up a download link for clients"

Security Considerations

  • All API credentials must be stored as environment variables
  • Implement input validation and sanitization for all tool parameters
  • Use HTTPS for all API communications
  • Follow the principle of least privilege for API token permissions
  • Audit log all write operations for compliance tracking

Resources

Changelog

VersionDateChanges
1.0.02026-04-01Initial MCP connector skill

Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.

Saved skills