Skip to main content
Glama
iMateo

fastpanel-mcp

site_files_upload

DestructiveIdempotent

Upload a local file or directory to a FastPanel site's web root over SSH, using rsync or scp. Resolves the correct owner and sets default permissions for web serving.

Instructions

Upload a local file or directory from THIS machine into a site's web root, over SSH (rsync, scp fallback). Resolves the site's index_dir + owner via site_get, transfers with your own ssh key (bytes never pass through the model), then chowns to the site's system user AND normalises perms on the destination subtree to FastPanel's web defaults (dirs 755, files 644) so nginx/PHP-FPM can serve it (local file modes are not relied on). rsync TRAILING-SLASH semantics: local_path 'build/' uploads the CONTENTS of build into the destination; 'build' (no slash) uploads the build dir itself, creating /build. dest_subpath is relative to the web root (omit to target the root). delete:true mirrors the source (rsync --delete removes remote files absent locally) — needs rsync, gated behind confirm. WRITE — set dry_run:true to preview, confirm:true to execute. Requires SSH configured (FASTPANEL_SSH_HOST).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deleteNorsync --delete: make the remote an exact mirror of local_path, removing remote-only files. Destructive.
confirmNo
dry_runNo
site_idYesSite id from sites_list
local_pathYesPath on THIS machine to a file or directory. Trailing slash on a dir uploads its contents.
dest_subpathNoDestination relative to the site web root (e.g. 'public' or 'wp-content/uploads'). Omit for the web root itself.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds rich behavioral detail beyond annotations: chown/perm normalization, bytes not passing through model, trailing-slash semantics, delete destructive behavior, and write flow with dry_run/confirm. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but well-structured: first sentence states purpose, then details key behaviors. Every sentence is informative, though slightly long. Front-loaded with essential info.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 params, no output schema), the description covers SSH prerequisites, permission normalization, rsync semantics, and write flow. No gaps in explaining behavior and usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, but the description adds crucial semantics: trailing-slash for local_path, relative destination for dest_subpath, and the role of dry_run/confirm. Compensates well for missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states upload of local file/directory to site web root via SSH, with explicit verb and resource. Distinguishes itself from siblings like site_file_put (single file) and site_files_deploy by specifying the mechanism and scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context: for bulk upload via SSH, with prerequisites (SSH configured), dry-run/confirm flow, and trailing-slash semantics. Implicitly differentiates from alternatives but lacks explicit when-to-use vs siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iMateo/fastpanel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server