jioaicloud-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIOAICLOUD_ID | Yes | Your Jio AI Cloud ID or login identifier. | |
| JIOAICLOUD_OTP | No | Optional OTP for first-time login only. | |
| JIOAICLOUD_MOBILE | Yes | Your Jio AI Cloud mobile number (e.g., 91XXXXXXXXXX). | |
| JIOAICLOUD_PASSPHRASE | Yes | Your Jio AI Cloud passphrase. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jio_loginA | Log in to JioAICloud using env credentials (Mobile + Passphrase). Uses saved session when possible. For first-time login on this machine, send OTP first (jio_send_otp / jio_verify_otp) or set JIOAICLOUD_OTP. |
| jio_send_otpA | Send login OTP SMS to JIOAICLOUD_MOBILE (needed only for first login when no local session exists). |
| jio_verify_otpA | Verify OTP and establish a session, then unlock with passphrase from env. |
| jio_unlock_passphraseB | Unlock account passphrase (2FA) using JIOAICLOUD_PASSPHRASE. |
| jio_auth_statusA | Show whether a local JioAICloud session exists (no secrets). |
| jio_import_sessionB | Import a browser userData JSON blob (from localStorage) to create a local session, then unlock with passphrase. |
| jio_logoutA | Clear the local saved session. |
| jio_storage_usageA | Get storage quota / usage for the logged-in account. |
| jio_list_filesB | List files/folders under a folder (defaults to root). |
| jio_list_photosC | List backed-up photos. |
| jio_list_videosC | List backed-up videos. |
| jio_list_documentsC | List backed-up documents. |
| jio_get_fileB | Get metadata for a single file by objectKey/id. |
| jio_search_filesC | Search files by keyword. |
| jio_backup_summaryA | Summarize photo/video/document/audio/other backup counts and bytes (first page sample per category). |
| jio_find_duplicatesC | Find duplicate files among photos/videos/documents (or a custom list). Groups by checksum when available, else name+size. |
| jio_duplicate_reportA | Return the last jio_find_duplicates report from this session. |
| jio_delete_filesA | Move files to trash by objectKey ids. dry_run=true by default. Real delete requires dry_run=false and confirm=true. |
| jio_delete_duplicatesA | Trash delete-candidates from the last jio_find_duplicates run. dry_run=true by default; real delete needs dry_run=false and confirm=true. |
| jio_download_fileC | Download a file by objectKey to the local downloads folder. |
| jio_export_inventoryB | Export an inventory of photos/videos/documents (or all) to JSON/CSV under downloads/. |
| jio_list_albumsA | List albums. kind=folder lists folders under a parent (default root) — these are the album folders used for organizing media. kind=board lists native JioAICloud Albums. |
| jio_create_albumA | Create an album. kind=folder creates a My Files folder (recommended for organizing photos/videos). kind=board creates a native JioAICloud Album; use jio_add_to_board to add existing Drive files. |
| jio_rename_albumB | Rename a folder album by objectKey/id. parentId should be the current parent folder key when known. |
| jio_move_to_albumA | Move files or folders into a folder album by destination albumId (folder objectKey). Pass optional items[] with name/objectType/sourceName for best results. For native board albums, use jio_add_to_board instead. |
| jio_add_to_boardA | Add existing Drive files into a native JioAICloud board album by boardKey. Files stay in My Files (link/copy into the board). Max 50 ids per call. |
| jio_delete_albumA | Delete albums. kind=folder moves folder album(s) to Trash by objectKey. kind=board deletes/leaves native board albums by boardKey (PUT /invites/boards/{id}/unjoin). dry_run=true by default; real delete requires dry_run=false and confirm=true. Board delete does not trash Drive files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
Most tools target distinct resources and actions (login, files, albums, duplicates). The only potential confusion is between move_to_album and add_to_board, and the multiple list_* commands, but descriptions clarify these differences.
All tools follow a consistent jio_verb_noun pattern with snake_case, making the action and target predictable. There are no mixed conventions or vague names.
At 27 tools, the server exceeds the 25-tool threshold and feels heavy for a cloud storage integration. While each tool is distinct, the count suggests the API surface could be consolidated.
Missing file upload (create) is a major gap for a cloud storage server. Also absent are file rename, restore from trash, and sharing. Album, backup, and duplicate management are well covered, but the core file lifecycle is incomplete.