Get the files from Simon
The agent needs the pack and will not guess a path. It creates a request and waits.
“Drop the September invoices here.”
MCP · Skill · HTTP
An agent shares files with a person, or gets files from a person.
Create a request or a send, paste the link, wait. The person never signs in. Bytes go straight to storage.
https://sharemeatsack.com/mcpPaste that into any MCP client. Grok connectors
Get files from Simon. Confirm who he is, create a request, paste the upload link, wait.
Put files on meatsack, or send them to Simon. Same page. Confirm him only if someone will open the link.
// the agent puts files on the page
{
"action": "send",
"title": "September invoices",
"files": [
{ "name": "invoice-q3.pdf", "type": "application/pdf", "size": 184320 },
{ "name": "notes.txt", "type": "text/plain", "size": 412 }
]
}
September invoices
Files for you
invoice-q3.pdfDownload
notes.txtDownload
How it goes
Step 1
The agent creates
One call builds a request or a send and returns a page link. No project to set up, no dashboard to learn.
Step 2
Files land on the page
Simon drops them, or the agent puts them. Either way the bytes sit on that page, not in chat.
Step 3
Share the link
Paste the page. Confirm him only if a person will open it. Put files on meatsack and send them to Simon are the same send.
What people use it for
Send them to Simon
The files are ready. The agent puts them on the page and pastes the link.
“These three are for you.”
Put this on meatsack
Same send. Nobody has to open it now. The page holds the files until they expire.
“Leave them here for later.”
One request per person
A job creates a separate upload page for every name on a list and collects them as they land.
Or just curl it
POST /api/v1/transfers
curl -sS https://sharemeatsack.com/api/v1/transfers \
-H 'content-type: application/json' \
-d '{
"action": "send",
"title": "September invoices",
"files": [
{"name": "invoice-q3.pdf", "type": "application/pdf", "size": 184320}
]
}'