Read-only FTP / SFTP surface — list_dir, get_file. No upload / delete / chmod tools.
Remote MCP server. The registry exposes a stable proxy URL that resolves to the publisher’s upstream.
https://mcp.amitte.com/amitte/ftp-tools@0.1.0Fallback · Local stdio shim via `npx @amitte-ai/cli connect amitte/ftp-tools` reads FTP_URL credentials from env.
Drop the JSON below into your MCP client's config file. Restart the client to load the new server.
~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"ftp-tools": {
"url": "https://mcp.amitte.com/amitte/ftp-tools@0.1.0"
}
}
}Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/ftp-tools.
Read-only Google Cloud Storage surface — list_buckets, list_objects, get_object_metadata, get_signed_url. Object bytes never traverse the model.
Read-only S3 surface — list_buckets, list_objects, get_object_metadata, get_signed_url. Object bytes are never returned through the agent — signed URLs are issued instead.
Sandboxed local FS access — list_dir, read_file, file_metadata. Every call is checked against a per-tenant path allowlist; symlinks are resolved server-side to prevent escapes.
Read-only GitHub surface — search_issues, get_pr, list_workflow_runs, get_file_contents. Auth via a fine-grained PAT or GitHub App.
Read-only GitLab surface — search projects + merge requests, list pipeline runs, and fetch file blobs at a ref.