# masv [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/getmasv/masv-mcp-server  
**GitHub Stars:** 5  
**npm Downloads (last month):** 347  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/masv

## Description
Provides tools to use MASV API. MASV is reliable and secure large file transfer service.

## Tools
Capabilities this server exposes over MCP:

- **get_packages** — Get team packages. These are packages sent by MASV team users directly to MASV. It does not include packages sent to Portals. To get full list of packages you need to get both team packages and portal packages
- **get_package** — Get package by id
- **get_portal_packages** — Get portal packages. These are packages uploaded by anyone to MASV Portals. Only packages that were uploaded to Portals returned by this tool. To get full list of packages you need to get both team packages and portal packages.
- **get_package_files** — Get list of package files
- **get_package_transfers** — Get all transfers of a package to storage. Transfer is a package delivery via MASV to cloud or on-premise (via MASV Storage Gateway) destination
- **update_package_expiration_date_and_time** — Update package expiration date and time. Also allows enable or disable unlimited storage. Additional package storage may incur charges, depending on your team subscription plan. Once expired the package and all of its files are deleted and can not be restored.
- **delete_package** — Delete a package by ID. This permanently removes the package and all its files and cannot be undone. Requires MASV_ALLOW_DELETE=true environment variable to be set.
- **get_activities** — Get activities. Activities are records of events that happened with MASV resources like packages, links and transfers. Each activity has assosiated events and can be in one of several states: pending, started, complete, cancelled, error. Full list of activity types: package_upload_to_masv (package upload from user or connected storage integration to MASV), package_download_from_masv (user downloads package), link_generation (new download link is added to the package), package_transfer_masv_to_cloud (package transfer from MASV to connected storage integration)
- **get_activity_events** — Get history of events for given activity. Activity gets event record every time it transitions to a new state. It is very useful to get events history to get more information about activity because it can transition states several times and activity only keeps track of its current state.
- **get_activities_information** — Get detailed information about all existing activities and their accurate states description. Always use this tool provide users with detailed explanation about activities and their states.
- **get_integrations** — Get list of connected integrations. Integration could be cloud or on-prem system like AWS S3, Frame.io, Dropbox, MASV Storage Gateway and many others
- **send_package_to_integration** — Send MASV package to connected integration. Integration could be cloud or on-prem system like AWS S3, Frame.io, Dropbox, MASV Storage Gateway and many others
- **list_files_on_integration** — List files on any integration (cloud or MASV Storage Gateway). Supports pagination — if more results are available, a cursor is returned; pass it back in the next call to get the next page.
- **transfer_files_from_integration** — Transfer files from a cloud integration (AWS S3, Azure, Dropbox, etc.) or MASV Storage Gateway to MASV. Creates a new package and initiates the transfer. Use list_files_on_integration first to get file information including IDs.
- **get_portals** — Get list of portals that belong to the team. Portals are used to collect files from external users. Each portal has a unique subdomain and can be configured with various settings like upload and download password, file type restrictions, connected integrations, metadata forms, etc.
- **get_portal** — Get a specific portal by ID. Returns detailed information about the portal including its configuration, recipients, connected integrations, and settings.
- **create_portal** — Create a new portal for collecting files from external users. Portals can be configured with access codes, download passwords, file type restrictions, custom branding, connected integrations, and more. Only 'name' and 'subdomain' are required - all other settings are optional.
- **update_portal** — Update an existing portal's configuration. Use this to modify portal settings like access controls, branding, file restrictions, and more.
- **delete_portal** — Delete a portal by ID. This permanently removes the portal and cannot be undone. Packages that were uploaded to this portal will remain accessible. Requires MASV_ALLOW_DELETE=true environment variable to be set.
- **get_team_members** — Get list of all team members. Returns member details including id (membership_id), email, name, policy, approval status, and teamspaces. Use this to get membership IDs needed for portal access_list when creating private portals.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "masv": {
    "command": "npx",
    "args": ["-y","@getmasv/masv-mcp-server"],
    "env": {
      "MASV_TEAM_ID": "",
      "MASV_API_KEY": "",
      "MASV_ALLOW_DELETE": ""
    }
  }
}
```

**Requires environment variables:** `MASV_TEAM_ID`, `MASV_API_KEY`, `MASV_ALLOW_DELETE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What masv does

The masv MCP server connects an MCP-compatible AI client to the MASV API. It gives an agent access to package records, portal configuration, activity data, storage integrations, and team-member information within a configured MASV team.

Package operations include listing team packages, retrieving a package by ID, finding packages uploaded through portals, examining package files, and reviewing transfer history. The server can also change package expiration dates and times. Portal operations cover listing and retrieving portals, creating portals, updating portal configuration, and deleting portals when deletion has been enabled.

The masv MCP server also exposes MASV activity history and descriptions of activity states. For connected storage, it can list integrations, send a package to an integration, browse files in cloud integrations or MASV Storage Gateway, and transfer files from those sources into MASV.

## How it works

The server runs as a Node.js MCP process and authenticates requests with a MASV team identifier and API key. An MCP client starts the process, then presents the server's tools to an AI assistant. Tool calls operate against the MASV API for the configured team.

Deletion is guarded separately from the other operations. The package and portal deletion tools require MASV_ALLOW_DELETE=true; without that setting, those destructive tools are not enabled for LLM use. The project is built and tested with Node.js 24 or newer.

## Setup and configuration

Run the published package directly with npx:

```bash
npx @getmasv/masv-mcp-server
```

A global npm installation is also supported:

```bash
npm install -g @getmasv/masv-mcp-server
```

Set these required environment variables before starting the process:

- `MASV_TEAM_ID`: the MASV team identifier.
- `MASV_API_KEY`: the MASV API authentication key.

Set `MASV_ALLOW_DELETE=true` only when the client should be allowed to use package and portal deletion tools. An MCP client configuration can start the server with `npx -y @getmasv/masv-mcp-server`, passing the credentials in its `env` object. The `-y` option accepts npm's execution prompt automatically.

## Tools and capabilities

Available tool groups include:

- Packages: list, inspect, update expiration, inspect files and transfers, and list portal uploads.
- Portals: list, inspect, create, update, and optionally delete portals.
- Activities: list activities, retrieve event history, and read activity-state information.
- Integrations: list connected storage, browse integration files, send packages to storage, and transfer files into MASV.
- Team: list members and their details.

The masv MCP server is suited to assistants that need to answer questions about MASV transfer state, review package contents or history, administer portals, or move files between MASV and configured storage integrations.

## Limitations and notes

This project is identified as experimental and has not completed the provider's internal verification process. Support and updates are provided on a best-effort basis. The supplied test suite runs offline and does not require MASV credentials, but normal API use does require valid team credentials.

The material does not document specific MASV API permissions beyond the credential requirement and the separate deletion flag. It also does not identify any client-specific setup beyond the standard MCP process configuration.

_Full upstream README: https://allmcps.com/mcp/masv/readme_