com.preesy/preesy
v1.0.0Print at a print shop with a short label instead of email or USB. Files expire on their own.
Endpoint health
online- Last checked
- 11/20/2026, 6:18:46 AM
- Latency
- 277 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.preesy%2Fpreesy
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.preesy/preesy": {
"url": "https://preesy.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
4 shown · authentication unknown
Create print session
create_print_session
Create a temporary Preesy session so a person can print a document from a public computer. No Preesy app or partnership is needed. The person can ask the staff to print via Preesy. If the staff do not know it, they just open preesy.com and enter the label (and the PIN, if set) in the Print box. The document expires automatically when its time is up, or earlier if the person asks you to expire it. If the person gave a label, use it as given. Otherwise pick a memorable label that is easy to say, from what the document is about. A common word is fine but likely to collide with others, so either pair it with a PIN, such as TICKET with PIN 1126, or make it unique with a combination that fits the context, such as FLIGHTANKARA, FLIGHT2026, or FLIGHT26. There is no fixed format. Do not put personal data in the label, and never put Preesy in the label. Labels are not unique. Never add a 4-digit PIN unless the person wants it. You may suggest one once when there is a reason, such as a common one-word label, and set it only if they say yes. A PIN cannot be added later. If the person wants one after the upload, call expire_print_session with the manage_token, then create_print_session again with the PIN. To change a label, call expire_print_session with that session's manage_token, then create_print_session with the new label and send the files and choices again. If expire fails, you may tell the person the old upload is still active, and still create the new upload. If expire succeeds, say nothing about the old upload. Depending on the context and what the person does, you may suggest a few print shops nearby or ask whether they want them, and you may suggest another way such as a hotel front desk. Ask for or use their location only if they agree, with your own tools. Never put the document, the label, the PIN, or the manage token into a maps or places query. This server takes no location. Choose lifetime_hours from when the person will print, before you upload. Use what they already said. Ask one short question only when you cannot tell a lifetime that matters, then upload. If you already know, upload without asking. Set lifetime_hours for when they will print. It must be from 1 to 168 hours. The document is deleted automatically, so a shorter time keeps less data. Omitting lifetime_hours stores the default, which is only a fallback. print_only defaults to false, so the page allows print and download. If the person already said whether they want print only, set print_only on create. If they did not say, create the session with print_only false, then ask the person once whether they want it print only, and if yes call set_print_only. One session can hold several files, as on the website, up to 10 files and 50 MB in total. Send files for more than one document, file for one, or text for plain text. Send file, files, or text, one of them. Each field is described in the input schema. one_time_access: If true, this is a single-use label. As soon as a file or the zip is printed or downloaded, it is removed from the system. Default false. Keep the manage_token in this conversation and use it for later get_print_session, set_print_only, and expire_print_session requests until the session expires. Each session has its own manage_token. If the conversation has several sessions, keep each token with its label and use the one that matches the session the person means. Share the token with the person only if they ask, and never post it anywhere else. The label and PIN cannot manage the session.
Connections
streamable-http
https://preesy.com/mcp