masv
Official# MASV MCP Server
> **⚠️ Experimental Server**: This is an experimental MCP server created to gauge interest and integration potential. It has not been subject to our rigorous internal verification processes. Further support and updates will be provided on a best effort basis. We want to hear from you ! If you have any questions or issues, please contact us at [support@masv.io](mailto:support@masv.io).
An MCP (Model Context Protocol) server that provides LLMs with tools to interact with the MASV API.
## What is MASV?
MASV is an easy-to-use and ultra-reliable managed file transfer service designed for teams of all sizes. It allows users to send and receive massive files without size limits, while ensuring data integrity and security through its robust cloud infrastructure that supports cloud, on-prem, and hybrid workflows.
Learn more https://masv.io/
## Installation
The server can be run directly with `npx` without installation, or installed globally if preferred:
```bash
# Run directly with npx (recommended)
npx @getmasv/masv-mcp-server
# Or install globally
npm install -g @getmasv/masv-mcp-server
```
## Configuration
### Required Environment Variables
The server requires the following environment variables to authenticate with the MASV API:
- `MASV_TEAM_ID` - Your MASV team identifier
- `MASV_API_KEY` - Your MASV API authentication key
### Optional Environment Variables
- `MASV_ALLOW_DELETE` - Set to `true` to allow LLM use package and portal deletion tools (default: `false`)
### MCP Client Configuration
Add the server to your MCP client configuration file:
```json
{
"mcpServers": {
"masv": {
"command": "npx",
"args": ["-y", "@getmasv/masv-mcp-server"],
"env": {
"MASV_TEAM_ID": "your-team-id",
"MASV_API_KEY": "your-api-key"
}
}
}
}
```
**Note**: The `-y` flag automatically confirms the package execution without prompting.
## Available Tools
The server provides the following tools for LLM interaction:
### Package Management
- `get_packages` - List team packages
- `get_package` - Get package details by ID
- `get_portal_packages` - List packages uploaded to portals
- `get_package_files` - List files in a package
- `get_package_transfers` - Get package transfer history
- `update_package_expiration_date_and_time` - Modify package expiration
- `delete_package` - Delete a package (requires `MASV_ALLOW_DELETE=true`)
### Portal Management
- `get_portals` - List all portals
- `get_portal` - Get portal details by ID
- `create_portal` - Create a new portal
- `update_portal` - Update portal configuration
- `delete_portal` - Delete a portal (requires `MASV_ALLOW_DELETE=true`)
### Activity Tracking
- `get_activities` - List activities and events
- `get_activity_events` - Get event history for an activity
- `get_activities_information` - Get detailed activity state descriptions
### Integration Management
- `get_integrations` - List connected storage integrations
- `send_package_to_integration` - Transfer package to connected storage
- `list_files_on_integration` - Browse files on cloud integrations
- `list_files_on_storage_gateway` - Browse files on Storage Gateway
- `transfer_files_from_integration` - Transfer files from storage to MASV (works with both cloud and MASV Storage Gateway)
### Team Management
- `get_team_members` - List team members and their details
## License
MIT
## Support
For questions, issues, or feedback please contact us at [support@masv.io](mailto:support@masv.io).
## Development
### Install dependencies
```
npm install
```
### Build
```
npm run build
```
### Use MCP server
In LLM chat application add command to start the server:
```
node /path/to/masv-mcp-server/build/index.js
```
To run MCP inspector to inspect and execute tools
```
npm run inspector
```
TDQS
Scored across 20 tools
Tools are grouped by resource (portals, packages, activities, integrations, team) with clear actions. Minor overlap between get_activities and get_activities_information could cause confusion, but descriptions differentiate them.
All tools use a consistent verb_noun pattern with underscores (e.g., create_portal, get_packages, transfer_files_from_integration). No mix of styles.
20 tools for a file transfer service is slightly above average but covers multiple resource types (portals, packages, activities, integrations, team). Each tool serves a clear purpose, and the count is reasonable for the domain.
Core workflows for portals and transfers are covered, but there is no explicit create_package tool (packages are created implicitly via transfers or portals). Missing update package operations beyond expiration, and no tool to manage package files or downloads directly. Notable gaps reduce completeness.