upload-files

Upload Files

Upload local files or user-provided attachments (images, XML, etc.) to the Gradio server so they become publicly accessible URLs. These URLs can then be passed to tools like htr_transcribe or the document viewer.

When to use

• User has attached images or XML files in the conversation
• User has local file paths that need to be accessible by a remote tool
• Any tool requires http/https URLs but you only have local data

If you already have http/https URLs (e.g. IIIF links, public image URLs), skip this skill entirely and pass them directly to the target tool.

Server URL

The upload target is the Gradio Space that backs the HTR MCP server:

https://riksarkivet-htr-demo.hf.space

Override with the HTR_SPACE_URL environment variable if set.

Upload workflow

Step 1: Save attachments to disk

If the user attached files in the conversation (not already on disk), save them first. Claude attachments are available as content in the conversation — write them to temporary files.

Step 2: Upload each file

For each file, POST to the Gradio upload endpoint:

curl -s -X POST "https://riksarkivet-htr-demo.hf.space/gradio_api/upload" \
  -F "files=@/path/to/filename.jpg"

Response is a JSON array of server paths:

["/tmp/gradio/abc123def/filename.jpg"]

Step 3: Construct public URLs

For each server path returned, construct the public URL:

https://riksarkivet-htr-demo.hf.space/gradio_api/file=/tmp/gradio/abc123def/filename.jpg

Pattern: {base_url}/gradio_api/file={server_path}

Step 4: Collect all URLs

Gather all constructed URLs before passing them to the target tool. Present the URLs to the user so they can verify the uploads succeeded.

Batch upload

You can upload multiple files in a single request:

curl -s -X POST "https://riksarkivet-htr-demo.hf.space/gradio_api/upload" \
  -F "[email protected]" \
  -F "[email protected]" \
  -F "[email protected]"

Response:

[
  "/tmp/gradio/abc123/page1.jpg",
  "/tmp/gradio/abc123/page2.jpg",
  "/tmp/gradio/abc123/page3.jpg"
]