pcloud-mcp
A hardened Model Context Protocol server for pCloud, written in Go.
Power your agent
Yayıncıdan kurulum. PlugMCP uç noktası değildir.
Host a copy with our keys and logs.
Registry'de henüz paketlenmiş bir sürüm yok. Deponun README dosyasını izleyin.
Uzak URL mi, yoksa makinenizde bir komut mu? İki kurulum arasındaki fark
PlugMCP’de çalıştır
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.
BaşlatYayıncıdan
A hardened Model Context Protocol server for pCloud, written in Go.
Hardened Model Context Protocol (MCP) server for pCloud, in Go. Path-traversal-proof downloads, OAuth-only auth, single static binary.
Give Claude (or any MCP host) access to your pCloud account — list, download, upload, organize, and share files in plain language. A single static binary with no runtime dependencies, designed so that an agent holding both a full-access cloud token and local filesystem access stays safely within the bounds you set.
Claude (MCP host)
│ stdio (MCP)
▼
pcloud-mcp ──OAuth token (POST body, never URL)──→ pCloud API (HTTPS)
│
│ every remote name → internal/safepath (validate, fail closed)
│ every local write → os.Root (kernel-enforced containment)
▼
your local disk — writes cannot escape the chosen directory
Once it's connected, you talk to your pCloud in plain language. For example:
It works two ways: locally through Claude Desktop (files land on your computer), or as a remote server so Claude.ai on the web or your phone can reach your pCloud from anywhere — see Remote access.
..), so every remote name is validated and every write goes through an os.Root
scoped to your destination. The kernel refuses any escape, even via a symlink planted mid-download.127.0.0.1, CSRF state compared in constant time,
token sent in the POST body (never the URL), stored 0600, never printed. No password flow.delete_file / delete_folder carry the MCP
DestructiveHint so your host can warn you before a recursive delete. pCloud routes deletes
to its time-limited Trash (plan-dependent recovery window) rather than erasing immediately —
treat it as destructive, not as a backup.govulncheck, staticcheck, and gosec run clean and gate CI; the build
toolchain is pinned. Zero third-party runtime dependencies beyond the official MCP SDK.A cloud-storage MCP server sits in an unusually sensitive spot: the host LLM holds a full-access cloud
token and can write to your local disk, and the file/folder names it acts on come from the cloud,
not from you — so they are untrusted input. A folder shared with you can legitimately be named ...
That makes "validate everything that comes back from the API, and contain every write" a design
requirement, not a nice-to-have.
This server is built around that from the ground up: every remote name is validated before it is used, and every write is contained by the OS kernel, so a name can never move a write outside the directory you chose. The full hardening table — each control and the class of attack it closes — is in SECURITY.md.
go install github.com/terraincognita07/pcloud-mcp/cmd/pcloud-mcp@latest
Or build from source:
git clone https://github.com/terraincognita07/pcloud-mcp.git
cd pcloud-mcp
go build -o pcloud-mcp ./cmd/pcloud-mcp
Or run the container (non-root, distroless):
docker build -t pcloud-mcp .
Register an app at https://docs.pcloud.com/my_apps/ and set its redirect URI to
http://127.0.0.1:53682/callback. Note the client id and client secret.
[!NOTE] pCloud has currently paused self-service registration of new OAuth apps. If the "create application" option is unavailable, that's a pCloud-side restriction, not a limitation of pcloud-mcp. Already-registered apps keep working — reuse credentials from an app you created earlier, or ask pCloud support to provision one (redirect URI
http://127.0.0.1:53682/callback). The server is OAuth-only by design and needs a client id / client secret to start; there is no password fallback.
Credentials are saved to your user config dir with 0600 permissions; the token is never printed.
export PCLOUD_CLIENT_ID=xxxxxxxx
export PCLOUD_CLIENT_SECRET=yyyyyyyy
pcloud-mcp auth
PowerShell:
$env:PCLOUD_CLIENT_ID = "xxxxxxxx"
$env:PCLOUD_CLIENT_SECRET = "yyyyyyyy"
pcloud-mcp auth
For Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"pcloud": {
"command": "pcloud-mcp",
"args": ["serve"]
}
}
}
That's it — serve reads the saved credentials and speaks MCP over stdio.
serve --http :8080 runs an authenticated HTTP server so Claude.ai in a
browser or on your phone can reach your pCloud from anywhere. It requires a
bearer token and a reverse proxy for HTTPS, and it hides the local-filesystem
tools (download/upload would write to the server's disk, not yours). Cloud-side
tools — browse, organize, share link, save text, fetch from URL — stay
available.
export PCLOUD_MCP_TOKEN=$(openssl rand -hex 32)
pcloud-mcp serve --http :8080 # bind behind a TLS reverse proxy
Full deployment (docker-compose + nginx / Caddy / Traefik + connecting Claude.ai) is in docs/SELF-HOSTING.md.
Hardening details, the specific attack each control closes, and the known (by-design) limitations of the MCP trust model live in SECURITY.md. The minimum audit gate, also enforced in CI:
go test ./... && go vet ./... && go run golang.org/x/vuln/cmd/govulncheck@latest ./...
Found a vulnerability? Please report it privately — see SECURITY.md.
go test ./... # all tests, incl. a real in-memory MCP integration test
go vet ./...
The code is layered one-directionally — cmd → mcpserver → {download, pcloud, safepath}, with
oauth/config wired directly in cmd (not imported by mcpserver) and cmd → httpserver
wrapping the MCP handler at the network boundary for HTTP mode —
and the security boundary isolated in internal/safepath. safepath and pcloud know nothing about
the filesystem layout or MCP, so the trust boundary stays in one auditable place.
MIT — see LICENSE.
Hardened Model Context Protocol (MCP) server for pCloud, in Go. Path-traversal-proof downloads, OAuth-only auth, single static binary.
Araçlar
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için stdio yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Pcloud yerel olarak stdio üzerinden çalışır.
Son kontrol: 2026-10-28. Hardened Model Context Protocol (MCP) server for pCloud, in Go. Path-traversal-proof downloads, OAuth-only auth, single static binary.