Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
A Model Context Protocol (MCP) server that exposes Nextcloud functionality as tools for AI assistants. Written in Go for minimal resource usage (~8 MB Docker image on scratch).
Lightweight Nextcloud MCP server in Go — 82 tools, multi-instance, 3MB Docker image
./setup.sh
This script creates the config directory and walks you through adding your first Nextcloud instance.
go build -ldflags="-s -w" -o nextcloud-mcp .
./nextcloud-mcp
The server starts on http://0.0.0.0:8080 with the MCP endpoint at POST /mcp.
Use the nc_config_add_instance tool (via your MCP client) or create the config file manually:
{
"default_instance": "home",
"instances": {
"home": {
"host": "https://cloud.example.com",
"username": "your-user",
"password": "your-app-password"
}
}
}
Config location: ~/.config/nextcloud-mcp/config.json (override with NEXTCLOUD_MCP_CONFIG env var).
docker build -t nextcloud-mcp .
docker run -p 8080:8080 -v ~/.config/nextcloud-mcp:/data nextcloud-mcp
The container stores config at /data/config.json. Mount a host directory to persist it across upgrades.
The server exposes 84 tools across 9 domains.
Every tool accepts an optional instance parameter to target a specific Nextcloud instance (defaults to the configured default).
All tools are registered globally and listed unconditionally — tools/list always returns the full set.
There is no per-session state: any client can call any tool at any time, and a server restart never
invalidates what a client knows about the toolset.
An earlier design hid each domain's tools behind per-session loader stubs to keep the initial list short. It was removed because MCP clients do not reliably keep a stable session — Claude's clients initialize a fresh session per poll or turn, and each fresh session fell back to the short list, making loaded tools appear to vanish. Clients that need a small tool surface defer tools on their side (e.g. tool search).
Acting on twenty items costs twenty tool calls, which is twenty round trips and twenty turns' worth of
tokens for what is a for-loop on the server. Four tools take a list instead — nc_deck_bulk_cards,
nc_tasks_bulk, nc_notes_bulk, nc_files_bulk — plus the filter-based nc_calendar_bulk_operations
for events. They are best effort: an item that fails does not stop the rest, and the result names the
ones that failed so only those need a retry. At most 100 items per call.
See docs/features.md for a complete tool reference with parameters, internals, and app requirements.
See docs/dev/architecture.md for the system design and component overview.
See LICENSE file.
Lightweight Nextcloud MCP server in Go — 82 tools, multi-instance, 3MB Docker image
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Nextcloud ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Lightweight Nextcloud MCP server in Go — 82 tools, multi-instance, 3MB Docker image
