Nextcloudmcp

Created By
bizneto10 months ago
A comprehensive Model Context Protocol (MCP) server for Nextcloud integration, providing AI agents with secure access to Nextcloud's file management, sharing, user administration, and system monitoring capabilities.
Overview

Nextcloud MCP Server - Overview

๐ŸŽฏ What is Nextcloud MCP Server?

The Nextcloud MCP Server is a comprehensive Model Context Protocol (MCP) implementation that bridges AI agents (like Claude) with Nextcloud cloud storage platforms. It provides secure, programmatic access to Nextcloud's full ecosystem through a standardized interface.

๐Ÿ—๏ธ Architecture

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”    โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”    โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚   Claude AI     โ”‚โ—„โ”€โ”€โ–บโ”‚  MCP Server     โ”‚โ—„โ”€โ”€โ–บโ”‚   Nextcloud     โ”‚
โ”‚   Assistant     โ”‚    โ”‚  (This Project) โ”‚    โ”‚   Instance      โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜    โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜    โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Core Components

  • MCP Server: Translates AI requests into Nextcloud API calls
  • Nextcloud Client: Handles authentication and API communication
  • Tool System: 37 specialized tools across 7 categories
  • Resource System: 6 dynamic resources for real-time data access
  • Prompt System: 5 workflow templates for complex operations

๐Ÿ› ๏ธ Tool Categories (37 Total)

File Management (7 Tools)

Complete WebDAV operations: list, upload, download, delete, move, copy, create folders

Sharing Management (4 Tools)

Full share lifecycle: create, list, update, delete shares with permissions and passwords

User Administration (7 Tools)

Complete user management: create, read, update, delete, enable/disable users (admin required)

Group Management (6 Tools)

Group operations: create, delete, list groups, manage memberships (admin required)

System Monitoring (3 Tools)

Server health: status, capabilities, connection testing

Comments System (3 Tools)

File comments: list, add, delete comments on files

Local File Management (5 Tools)

Efficient file processing: download to local cache, process, upload back

Activity Monitoring (2 Tools)

Track activities: file operations, shares, user actions, security events

๐Ÿ“Š Resources System (6 Resources)

Dynamic resources provide real-time access to Nextcloud data:

  • nextcloud://files - Root directory listing
  • nextcloud://shares - All shares overview
  • nextcloud://users - User directory
  • nextcloud://groups - Group listing
  • nextcloud://status - Server status
  • nextcloud://capabilities - Server capabilities

Server Config

{
  "mcpServers": {
    "nextcloud": {
      "command": "node",
      "args": [
        "/path/to/nextcloud-mcp-server/dist/index.js"
      ],
      "env": {
        "NEXTCLOUD_URL": "https://your-nextcloud-server.com",
        "NEXTCLOUD_USERNAME": "your-username",
        "NEXTCLOUD_PASSWORD": "your-password-or-app-password"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
bizneto
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine โ€” no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
AI Work Market โ€” USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` โ€” get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` โ€” get calldata for the seller to submit a proof URI - `release_funds_quote` โ€” get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` โ€” replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` โ€” generate a signed agent card with marketplace attestation - `agent_search` โ€” tf-idf search over the live agent catalog - `agent_reputation` โ€” server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` โ€” live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` โ€” contract semantics, lifecycle, call guides, failure modes - `events_subscribe` โ€” SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago