Pandafile MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PANDAFILE_API_KEY | Yes | Required. Your Pandafile API key: pf_live_…, or pf_test_… for test mode. Without it the server still starts, and every tool answers with setup instructions. | |
| PANDAFILE_BASE_URL | No | Optional. The Pandafile API base URL. Only for testing against a local Pandafile server. | https://pandafile.co/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Pandafile (https://pandafile.co) sends big files with a link. Use these tools to:
send local files or whole folders (send_files) or files at https URLs (send_from_urls) and get a share link,
look up, change, delete transfers and add or remind recipients,
collect files from other people with file requests (an upload page),
check the account's plan, limits and usage (get_account). Recipients get an email with their own link (never with a test key: pf_test_ keys make test transfers that email nobody and expire after 24 hours). Share links look like https://pandafile.co/d/. Files are stored in Helsinki, Finland (EU).
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 |
|---|---|
| send_filesA | Upload local files and/or folders to Pandafile and get a share link (https://pandafile.co/d/). Folders are sent with their structure. Large files are fine (resumable, chunked uploads); the call returns when the upload is complete. If recipients are given, each gets an email with a personal download link. Returns the link, id, expiry and sizes. Only send files the user asked you to send. |
| send_from_urlsA | Create a Pandafile transfer from files at public https URLs: Pandafile downloads them itself (no local upload). Waits up to ~20 seconds. status "ready": the link works now. status "uploading": big files are still downloading – call get_import_status with the id until it is "ready" (or "failed"). Recipients are emailed when it is ready. |
| get_import_statusA | Progress of a transfer created with send_from_urls: per file bytes received, then "ready" (the link works) or "failed" (with the error; the transfer is then deleted). |
| list_transfersA | The account's transfers, newest first, with link, size, expiry and download counts. view "active" (default: live and still uploading) or "history" (expired, deleted, blocked). Pass next_cursor as cursor for the next page. |
| get_transferA | One transfer in detail: link, status, expiry (and the latest expiry possible), files, recipients (who was emailed, who downloaded), latest downloads, approvals/comments from recipients and link statistics (views, downloads, countries). |
| add_recipientsA | Email the transfer's link to more people: each new address gets an email with a personal download link. Addresses already on the transfer are skipped. |
| remind_recipientA | Email a recipient of the transfer their personal link again (and turn their reminders back on). At most twice an hour per recipient. |
| update_transferA | Change a live transfer: title, message, expiry (later only, Pro/Team, at most 90 days after it was sent – get_transfer shows latest_possible_expiry) and the download password (set a new one, or remove it with remove_password). Only the fields you give change. |
| delete_transferA | Delete a transfer now: its files are removed for good and the link stops working for everyone. This cannot be undone – confirm with the user first. |
| create_file_requestA | Create a file request: an upload page (link) anyone can use to send files to this account – e.g. to collect photos or documents from a client. Uploads show up as transfers. Needs a live key on Pro/Team. |
| list_file_requestsA | The account's file requests (upload pages) with their links, whether they are open and how many uploads came in. Pass next_cursor as cursor for the next page. |
| close_file_requestA | Stop a file request from accepting uploads (its upload page then says it is closed). Files already uploaded stay. It can be reopened from the dashboard. |
| get_accountA | The account behind the API key: plan, limits (max bytes per transfer, expiry days, features), usage (this week / month, storage) and whether the key is a test key. |
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 13 tools
Each tool maps to a distinct resource and action: transfers (send/get/list/update/delete), recipients (add/remind), imports (send_from_urls/get_import_status), and file requests (create/list/close). The potentially ambiguous pair send_files vs send_from_urls is clearly separated by source (local upload vs public HTTPS URLs), and get_transfer vs get_account vs get_import_status target different entities. No two tools could be plausibly confused in normal use.
All 13 tools use consistent snake_case verb_noun naming (send_files, get_transfer, list_transfers, update_transfer, delete_transfer, create_file_request, close_file_request). The verb set is small and predictable — send/get/list/add/remind/update/delete/create/close — with no camelCase or stylistic mixing.
13 tools sits squarely in the well-scoped range for a file-transfer service with three sub-domains (transfers, imports, file requests). Each tool covers a distinct operation and none appears redundant or like filler.
Transfers have full lifecycle coverage (send, list, get detail, update, delete) plus recipient management, and file requests cover create/list/close. Minor gaps remain: no remove_recipient, no get_file_request for a single upload page's detail, and no reopen_file_request (the description says reopening is dashboard-only), which slightly limits programmatic file-request management.