BulkPublish for AI agents
BulkPublish schedules and publishes social content across multiple channels at once, then reports back on how each post performed over time. 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.
What agents do in BulkPublish.
Check performance across channels
Pull a summary of post performance across every connected channel before planning the next batch.
Review what's already scheduled
List upcoming posts across all channels to catch anything that overlaps or clashes.
Check usage before a big push
Check current plan and API usage limits before scheduling a large batch of posts.
10 BulkPublish actions, graded by risk.
Every BulkPublish action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
10Look things up. Allowed by default.
- bulkpublish.list_mediaList Media
- bulkpublish.list_postsList Posts
- bulkpublish.list_labelsList Labels
- bulkpublish.list_activityList Activity
- bulkpublish.list_channelsList Channels
- bulkpublish.get_plan_usageGet Plan Usage
- bulkpublish.list_notificationsList Notifications
- bulkpublish.get_analytics_summaryGet Analytics Summary
- bulkpublish.get_api_request_usageGet API Request Usage
- bulkpublish.get_platform_availabilityGet Platform Availability
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
BulkPublish in three steps.
- 01Your users connect BulkPublishThey add their BulkPublish api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls BulkPublish through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('bulkpublish', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How BulkPublish connects.
Users add their BulkPublish 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 BulkPublish 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
Use BulkPublish from any agent.
BulkPublish and Arc0, answered.
Can I use BulkPublish with Claude, ChatGPT or Cursor?
Yes. Connect BulkPublish 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 BulkPublish actions you allow.
How do users connect BulkPublish?
Users add their BulkPublish 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.
Which BulkPublish actions can my agent take?
10 in total: 10 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in BulkPublish?
Yes. Allow read actions and deny writes in the BulkPublish policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call BulkPublish too?
Yes. The same BulkPublish connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug BulkPublish into your agent.
Your users connect BulkPublish once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan