The SendSafely Local MCP Server is currently in limited Beta. Please contact your account manager if you would like to request access. 

The SendSafely Local MCP Server gives your AI agent access to the features and functions available in your SendSafely account. You can send encrypted files, download and decrypt, manage recipients, access workspaces, and review package activity using plain language. 

The article provides examples of common functions. For instructions on setting up the Local MCP Server, see this article.

Sending a Transfer Package

Use the Local MCP to send Transfer packages. The order the MCP will execute tasks when sending a transfer package is below:

1. Create package
2. Upload file(s) - you must explicitly approve this step each time a file is uploaded
3. Add recipient(s)
4. Configure options (expiration, label, etc.) — optional, if not provided the MCP will use the defaults set up on your account profile
5. Finalize — the AI agent will ask whether to auto-email recipients the secure link before finalizing

Example prompts for sending a package: 

Creating Packages

Create a new package
> "Create a new SendSafely package for me."

Upload a file
> "Upload ~/Documents/contract.pdf to my current package."
> "Add both setup.md and config.json to the package I just created."

Add a secure message to a package
> "Add the message 'Please review by Friday — let me know if you have questions.' to the package."

Managing Recipients

Add a recipient (email verification — default)
> "Add alice@example.com as a recipient."

Add a recipient with SMS verification
> "Add bob@example.com as a recipient with SMS verification to +1-555-867-5309."

Add multiple recipients at once
> "Add alice@example.com, bob@example.com, and carol@example.com as recipients."

Remove a recipient
> "Remove alice@example.com from package 3B98-KK8J."

Configuration Package Options

Set expiration
> "Set this package to expire in 7 days."

Enable watermarking
> "Enable watermarking on this package."

Restrict saving and printing
> "Restrict file saving and printing on this package."

Set a per-recipient access limit 
> "Limit each recipient to 3 downloads on this package."

Finalizing & Sending

Finalize with auto-notify
> "Finalize the package and email the link to all recipients."

Finalize without notification
> "Finalize but don't notify — I'll share the link myself."

Finalize as password-protected (anonymous)
> "Finalize this package as password-protected — I'll share the password separately."
> Note: Do NOT also add named recipients when using this method.

Deleting a Package

Delete a package
> "Delete package 3B98-KK8J."

Receiving & Accessing Packages

The Local MCP can be used to monitor sent and received packages (Dropzone or Transfer packages). To download or read package content, the agent must be provided with the fully keyed secure link, or be set up as a trusted device. The agent will always request approval before downloading, or reading package content.

Example prompts for receiving & accessing packages: 

List received packages
> "Show me all packages I've received."

List sent packages
> "Show me all packages I've sent."

Get package information
> "Get info on package 3B98-KK8J."
> "What files are in this package? [paste secure link]"

Download package files
> "Download all files from package 3B98-KK8J to ~/Downloads/audit-files/."

Read a downloaded file
> "Read the contents of the file I just downloaded from that package."

Read a package's message
> "Show me the message on package 3B98-KK8J."

Workspaces

You can use the Local MCP to create and manage Workspaces. Note that Workspace collaborators are never auto-notified. When you add a collaborator, or recipient to a workspace, SendSafely does not send them an email with the secure link. You must share the secure link manually so they can access the Workspace. The AI agent will remind you to do so.

Example prompts for using workspaces: 

Create a workspace
> "Create a new workspace called 'Project Phoenix — Shared Assets'."

List workspaces
> "List all my SendSafely workspaces."

Create a directory
> "Create a folder called 'Contracts' in my Phoenix workspace."

Rename a directory
> "Rename the 'Drafts' folder to 'Final Versions'."

Move a directory
> "Move the 'Invoices' folder into 'Archive'."

Delete a directory
> "Delete the 'Old Files' folder from my Phoenix workspace."

Upload a file to a workspace directory
> "Upload invoice_oct.pdf to the 'Invoices' folder in my Phoenix workspace."

Download a file from a workspace directory
> "Download sow_v2.pdf from the 'Contracts' folder in my Phoenix workspace."

Update a collaborators role 
> "Promote bob@example.com to MANAGER on my Q3 Reports workspace."

Get activity log
> "Show me the activity log for package 3B98-KK8J."

Making the MCP a Trusted Device 

If you wish to trust your AI agent with access to your SendSafely packages without providing a secure link, you can add it as a SendSafely Trusted Device. When trusted, SendSafely will encrypt the keycodes for all new items to the device's public key.

Note on existing packages: To grant access to older items, log into the SendSafely portal from another browser that's already a Trusted Browser for your account. That login step prompts SendSafely to sync your existing keycodes to this new device

Example prompts : 

Generate trusted device keypair
> "Register this machine as a trusted device on my SendSafely account."

Verify credentials
> "Verify my SendSafely credentials are working."