You're viewing a demo portfolio

Join the waitlist
PRSM

meta-tools.upload_file

Active

Tool of Vee3

declared in 1.27.1

Reserve a direct upload slot for a local file. Pass the desired file_name only. The name may omit an extension. Vee3 returns an upload_code. Install the uploader once with `npm install -g @vee3/upload` (requires Node 18+), then run `vee3-upload {upload_code} {file_path}` in the terminal. The CLI resolves the code to a signed upload URL, streams the local file to Vee3 storage, and prints the stored file_name after the upload finishes. Use that file_name in meta-tools.list_uploaded_files and other capabilities. The CLI does not need an API key. If installation fails with a TLS or certificate error (common on networks that inspect HTTPS traffic), use Node 22.15 or newer and run with NODE_OPTIONS=--use-system-ca, or configure npm to trust your network's root certificate. Files can be up to 2 GB and are stored for 14 days. After the upload is detected, Vee3 bills 1 token per 20 MiB, rounded up with a minimum of 1 token. Upload codes can be resolved within 60 minutes of reserve. Use `meta-tools.list_uploaded_files` to list stored uploads for follow-up work. Cost = 0 tokens to reserve. After upload completes, billing is 1 token per 20 MiB, rounded up (minimum 1 token).

Parameters schema

{
  "type": "object",
  "title": "upload_fileArguments",
  "required": [
    "file_name"
  ],
  "properties": {
    "file_name": {
      "type": "string",
      "title": "File Name",
      "maxLength": 255,
      "description": "Desired file name for the uploaded file. Extension is optional and is replaced based on detected file type."
    }
  }
}

What this tool wraps· 0 endpoints

min confidence0.700.50

No endpoints wrapped at confidence ≥ 0.70.

Parent server

Vee3

https://github.com/Vee3io/Vee3

1/7 registries
View full server →
meta-tools.upload_file — Vee3 — PRSM MCP