Upload-Post for AI agents

Upload-Post publishes and schedules content across multiple social networks from one place, used by creators and marketing teams managing several channels at once. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Social mediaAPI keyMCP + RESTupload-post.com
AUDIT LOG · UPLOAD-POSTPOLICY: acme-support
09:41:07 · claude · u_8f2read
upload_post.list_profiles
List Profiles✓ allowed · 212ms
09:41:08 · claude · u_8f2read
upload_post.get_upload_status
Get Upload Status✓ allowed · 164ms
09:41:09 · claude · u_8f2write
upload_post.create_profile
Create Profile✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
upload_post.cancel_scheduled_post
Cancel Scheduled Post✕ blocked · policy: deny
EVERY UPLOAD-POST CALL, ON THE RECORD
01 · USE CASES

What agents do in Upload-Post.

01

Schedule a post across platforms

Queue a post to publish at a set time across connected social accounts.

02

Check upload status

Look up whether a scheduled post published successfully, a read-only check.

03

Confirm before canceling a scheduled post

Check with the user before canceling a scheduled post, since it removes it from the queue entirely.

02 · ACTIONS

12 Upload-Post actions, graded by risk.

Every Upload-Post action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

6

Look things up. Allowed by default.

  • upload_post.list_profiles
    List Profiles
  • upload_post.get_upload_status
    Get Upload Status
  • upload_post.list_upload_history
    List Upload History
  • upload_post.list_scheduled_posts
    List Scheduled Posts
  • upload_post.list_cached_post_analytics
    List Cached Post Analytics
  • upload_post.list_platform_destinations
    List Platform Destinations

write

5

Create and change things. Allow, or ask the user first.

  • upload_post.create_profile
    Create Profile
  • upload_post.update_scheduled_post
    Update Scheduled Post
  • upload_post.enqueue_post
    Enqueue Post
  • upload_post.publish_post
    Publish Post
  • upload_post.schedule_post
    Schedule Post

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • upload_post.cancel_scheduled_post
    Cancel Scheduled Post
03 · HOW IT WORKS

Upload-Post in three steps.

  1. 01Your users connect Upload-PostThey add their Upload-Post api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Profile” can wait for the user, and “cancel Scheduled Post” can be denied outright.
  3. 03Any agent can actYour agent calls Upload-Post through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('upload_post', {
  read: 'allow',
  write: 'ask',        // create_profile
  destructive: 'deny',  // cancel_scheduled_post
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Upload-Post connects.

Users add their Upload-Post api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Upload-Post connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Upload-Post from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Upload-Post and Arc0, answered.

Q01

Can I use Upload-Post with Claude, ChatGPT or Cursor?

Yes. Connect Upload-Post to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Upload-Post actions you allow.

Q02

How do users connect Upload-Post?

Users add their Upload-Post api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Upload-Post actions can my agent take?

12 in total: 6 read, 5 write and 1 destructive, such as “create Profile”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Upload-Post?

Yes. Actions like “cancel Scheduled Post” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Upload-Post too?

Yes. The same Upload-Post connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Upload-Post into your agent.

Your users connect Upload-Post once, under your brand. Your agent gets 12 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan