Use cases

What this is

Three concrete shapes cover most of what an MCP-connected agent does in Dropslate: publish files from your own computer, batch a week of posts, and answer questions about what’s scheduled.

Publish files from your computer

The exact case the publish_files prompt automates: point Claude Code, Cursor or Claude Desktop at local files and describe where and when. The agent:

1. Calls dropslate_whoami to confirm the workspace and its timezone.
2. Calls dropslate_list_accounts to get real account ids - never guessed.
3. For each file: dropslate_create_upload, PUTs the bytes from your machine, polls dropslate_get_media until ready.
4. Calls dropslate_plan_post and shows you its table.
5. Waits for your explicit confirmation.
6. Calls dropslate_create_post with confirm: true.
7. Calls dropslate_get_post for each and reports its status with the absolute time.

See Files from your computer below for how the upload URL itself works.

Plan a week in one conversation

Describe a recurring pattern (“Tuesday and Friday at 18:00 Kyiv, three weeks, alternate between these two videos”) and the agent calls dropslate_plan_post once per slot, showing every table before calling dropslate_create_post for each - see Getting started → Plan a week.

Ask what’s scheduled

A read-only question - “what’s queued for next week,” “did the Tuesday post to Instagram go out” - only needs dropslate_list_posts and dropslate_get_post. This works even with a read-only key or on the Free plan, since no write tool is involved.

Files from your computer (Cowork, Claude Code)

dropslate_create_upload {filename, mime, size} returns {mediaId, uploadUrl, expiresAt}. uploadUrl is single-use and lives for one hour - its appearing in the chat history is not a leak by itself. The agent then PUTs the bytes from a local shell:

curl -X PUT "<uploadUrl>" -H "Content-Type: video/mp4" --data-binary @launch.mp4

Invoke-WebRequest -Method Put -Uri "<uploadUrl>" -ContentType "video/mp4" -InFile .\launch.mp4

Content-Length must equal the size sent in the request. Then dropslate_get_media {mediaId} until status: ready, and that mediaId goes into dropslate_plan_post. The file is never uploaded twice.