Skip to main content
Glama

Related Servers

Alternatives to cldsh

  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that provides an interface for interacting with the Cloudinary API to manage media assets and cloud configurations. It enables secure resource management through API keys and OAuth2 authentication within MCP-compliant environments.
    1,809 npm
    MIT

Related Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    A cloud replacement for mcp-server-filesystem that provides 30 tools for S3, Azure Blob, and Google Cloud Storage, deployable locally via STDIO or remotely over HTTP/WebSocket with OAuth 2.1 authentication.
    25 npm
    3
    -
  • A
    license
    C
    quality
    C
    maintenance
    It exposes the full official Immich API (276 tools across 41 groups) to MCP clients, letting them search and manage assets, albums, people, tags, memories, shared links, users, jobs and admin settings. It supports file uploads and downloads, stdio or streamable HTTP transports, and filtering/read-only safety modes.
    276
    47 npm
    MIT
  • A
    license
    C
    quality
    A
    maintenance
    Selectel S3 MCP server and Go CLI: browse, preview and restore files in a bucket. Read-only by default; write, delete and admin tools only behind switches, destructive calls confirmed by a person.
    13
    MIT
  • A
    license
    C
    quality
    A
    maintenance
    Yandex Cloud S3 MCP server and Go CLI: browse, preview and restore files in a bucket. Read-only by default; write, delete and admin tools only behind switches, destructive calls confirmed by a person.
    14
    MIT

TDQS

A3.9/5.0

Scored across 11 tools

Disambiguation4/5

Most tools target a clearly distinct operation (get_url, info, upload, download, delete, mkdir, account). Two pairs blur: cloudinary_move explicitly also moves folders, which overlaps cloudinary_rename_folder, and cloudinary_tree overlaps cloudinary_list since the tree includes per-folder asset listings; the descriptions mitigate but do not fully eliminate the misselection risk.

Naming Consistency4/5

Every tool uses the same cloudinary_ prefix with snake_case, which is highly predictable. Minor deviation: most names are verb-based (get_url, list, upload) while a few are bare nouns (info, tree, account), so the pattern isn't perfectly uniform.

Tool Count5/5

11 tools sits squarely in the well-scoped range and each maps to a real asset-management need (listing, metadata, transfer, folder ops, account state). Nothing appears redundant enough to drop.

Completeness4/5

The core lifecycle is covered: browse (list/tree/info), transfer (upload/download), organize (mkdir/move/rename_folder), remove (delete), URL generation, and account introspection, with a consistent confirmation flow for destructive ops. Gaps exist around asset metadata updates (tags are reported by info but there is no tool to set them) and explicit asset rename/public_id changes outside move.

Maintenance

ActivityMaintained
ResponsivenessNo issues