---
title: "Paperclip integration with Bolta"
description: "Connect Bolta to Paperclip as a custom MCP connector so a social media agent drafts posts in your voice. Per-action permissions, a Bolta review queue, and nothing published without your yes."
canonical_url: "https://bolta.ai/integrations/paperclip"
markdown_url: "https://bolta.ai/integrations/paperclip.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Paperclip integration with Bolta

Source: https://bolta.ai/integrations/paperclip
Last updated: 2026-11-21

Connect Bolta to Paperclip as a custom MCP connector so a social media agent drafts posts in your voice. Per-action permissions, a Bolta review queue, and nothing published without your yes.

## Summary

Give your Paperclip agent team a social media tool that waits for your yes

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Give a content or social agent on your org chart a standing job to draft posts each week
- Let a heartbeat schedule wake the agent so drafts are waiting on Monday morning
- Have a research agent hand a product update to the social agent, which drafts it in your voice
- Keep write actions on Ask first so a person confirms before the agent changes anything in Bolta
- Share one Bolta connection across several agents, with different ones allowed to read or draft
- Ask a reporting agent to read Bolta analytics and feed the numbers into next week's plan

## Limitations and boundaries

- Confirmed from Paperclip's official docs: the Connectors page accepts a remote MCP server URL, and signs in with OAuth, an API key sent as an Authorization header, or no auth. Each action can be set to Allowed, Ask first or Off.
- Not confirmed: which MCP transport Paperclip uses (Streamable HTTP or SSE). Bolta's server uses Streamable HTTP, so the connection is expected to work but has not been tested end to end.
- Not confirmed: whether Paperclip's OAuth client registration works against mcp.bolta.ai. If it does not, use a Bolta API key instead.
- Not confirmed: whether every agent runtime inside Paperclip can use the connector or the skill. Test with the agent you plan to rely on.
- There is no Bolta-specific Paperclip plugin. This page uses Paperclip's own custom MCP connector and, optionally, its skills import.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## Install Paperclip if you have not

Run npx paperclipai@latest onboard --yes in a terminal (it needs Node.js 24.11 or newer), then open http://localhost:3100. Paperclip is self-hosted, so you do not need a Paperclip account.

## Decide which brands the agent team may touch

In Bolta, work out which organization and brands this team should reach. One connection covers one organization, and you tick the brands when you sign in.

## Open Connectors and choose Connect your own MCP server

In Paperclip, go to the Connectors page and pick the option to connect your own MCP server.

## Paste Bolta's address

Paste https://mcp.bolta.ai/mcp as the full URL. Paperclip asks the server what it needs and walks you through the sign-in: OAuth, an API key, or none.

## Sign in with OAuth, or paste an API key

If Paperclip opens a browser window, sign in to Bolta and tick the brands it may reach. If it asks for an API key instead, create one in Bolta under Settings, API Keys (it starts with bolta\_sk\_), tick only the permissions the agent needs, and paste it. Paperclip sends it as an Authorization header. Bolta's other setup guides use the value Bearer followed by the key, so if a plain key is rejected, use Paperclip's custom header option with that format.

## Set the action permissions

Paperclip reads the action list and lets you set each action to Allowed, Ask first or Off on the Permissions tab. Leave reads on Allowed and set writes such as publish, approve and delete to Off or Ask first. Paperclip's docs advise starting with every write Off and promoting deliberately. Then limit which agents may use the connector.

## Optional: install the Bolta skill, then assign it

Paperclip imports skills at company level and accepts an npx skills add command as the source: npx skills add boltaai/bolta-skills --skill bolta. Importing does not attach it to anyone, so assign it to your social media agent afterwards.

## Check the agent sees the right brands

Ask the agent to list your Bolta workspaces and accounts. If a brand is missing, reconnect and tick it.

## Ask for drafts and approve them in Bolta

Ask for a post. It is saved as a draft. Read it and approve it in Bolta, or in a chat with an approval step, before anything goes public.

## What Paperclip is, and why that changes the setup

Paperclip is not a chat window. It is a self-hosted control plane that runs a company of agents, with an org chart, budgets, approval gates and scheduled heartbeats. It is open source under the MIT licence and is self-hosted, opening at http://localhost:3100, with no Paperclip account. The agents inside it can run on runtimes such as Claude Code, Codex, Cursor and OpenClaw. For social media that means Bolta is not something you talk to directly. It is a shared tool the agent team uses, and you decide which agents get it.

## Give your social media agent a job and a schedule

A connector alone does nothing until an agent has a reason to use it. 1. Create a content or social role: Add an agent to the org chart whose job is social drafts. Give it a one-line brief such as: draft posts for our brands in Bolta and save them for review. 2. Allow only that agent to use Bolta: Paperclip lets you decide which agents may use a connector. Start with the social agent only. 3. Add a heartbeat if you want it on a schedule: Paperclip agents can wake on a heartbeat. Pair that with a Bolta routine, or simply ask the agent to draft each time it wakes.

## Per-action permissions: why writes should start Off

After you connect, Paperclip reads the server's actions and lets you set each one to Allowed, Ask first, or Off. Its docs recommend starting with all writes Off. These are Paperclip's own settings and sit on top of Bolta's. They are a second layer, not a replacement. After you refresh the actions, Paperclip's docs warn that a newly found action can become active under your existing policies, so review the list again. Setting: Allowed; Good for: Reading, no side effects; Bolta example: list-accounts, list-inbox-items, get-account-analytics | Setting: Ask first; Good for: Changes you want to see before they happen; Bolta example: save-post, create-routine | Setting: Off; Good for: Actions the agent should never take; Bolta example: publish-post, approve-many-posts, delete-post

## Two gates before anything goes public

Paperclip has its own approval workflow and governance for agent actions. Bolta has a review queue and its own rule that nothing is approved, scheduled or published until a person says yes. Keeping both gives you two places to catch a bad post. If Paperclip is set to Ask first, you confirm the action there, and the post still lands in Bolta as a draft. Bolta refuses or routes to review anything the connection is not allowed to publish. Paperclip's budgets and activity log show what the social agent did and what it cost. Do not rely on prompts alone. Use the permissions, not a sentence telling the agent to be careful.

## Install the Bolta skill, then assign it

Paperclip can import skills at company level from a GitHub repo, a skills.sh URL, or an npx skills add command. For Bolta the source is npx skills add boltaai/bolta-skills --skill bolta. Importing it does not attach it to any agent, so assign the skill to your social media agent afterwards. Paperclip's docs say skill syncing is unsupported for some runtimes, openclaw\_gateway among them, where you manage skills inside the remote runtime. Confirm yours supports it.

## Budgets and the audit log for a social agent

Paperclip's README says you can track reported spend, get threshold alerts and pause work at configured limits, set at company, agent or project level. It also records approvals and cost events as activity you can audit. Setting a limit on the social agent is a way to cap a loop that keeps retrying. Bolta holds the drafts in its own inbox, so if something looks off you can compare what Paperclip logged with what actually arrived in Bolta.

## Which agent runtime should hold the connection

Paperclip can run agents on Claude Code, Codex, Cursor and OpenClaw. The Bolta connector is set up once at company level, then you choose which agents may use it. Our research could not confirm that every runtime can use a company connector. Try it with the runtime your social agent already uses, and ask it to list your Bolta workspaces before you rely on it.

## After Bolta changes: refresh the actions

Paperclip reads Bolta's action list when you connect. If Bolta adds or renames a tool later, use Refresh actions so Paperclip reads the list again. Paperclip's docs warn that a newly found action can become active under your existing policies. Open the Permissions tab afterwards and confirm that writes are still Off or Ask first.

## Can Paperclip agents post to social media through Bolta?

Yes, in principle, through Paperclip's custom MCP connector. The agent drafts and Bolta publishes to the networks you have connected once you approve. The end-to-end connection is not yet tested by us.

## How do I add the Bolta MCP server to Paperclip?

Open Connectors, choose Connect your own MCP server, and paste https://mcp.bolta.ai/mcp. Paperclip then detects the sign-in type. You can also paste an existing MCP client config.

## Does Paperclip use OAuth or an API key for Bolta?

Either. Paperclip asks the server what it needs. OAuth opens a browser sign-in, while an API key is sent as an Authorization header. Which one Bolta triggers in Paperclip is not tested by us. Bolta keys are made under Settings, API Keys.

## Can my Paperclip agent publish without my approval?

No. Bolta does not approve, schedule or publish until a person says yes. You can also set publish and approve to Off in Paperclip's action permissions for a second layer.

## How do I install the Bolta skill in Paperclip?

Import it at company level in Paperclip, using npx skills add boltaai/bolta-skills --skill bolta as the source, then assign it to your social media agent. Importing alone does not attach it.

## Do I need a Paperclip account?

No. Paperclip is self-hosted and open source, and onboarding runs on your machine. You do need a Bolta account and at least one connected social account to publish.

## Can several Paperclip agents share one Bolta connection?

Yes. The connector is set up once, and you choose which agents may use it. One connection covers one Bolta organization.

## What happens when an OAuth token expires?

If Paperclip cannot renew it, the agent loses Bolta access until you reconnect and sign in again. Paperclip's docs say the provider decides whether a refresh token is issued, and we have not tested this with Bolta. An API key avoids it, but keep it private and replace it if it is revoked.

## Is there a Bolta plugin for Paperclip?

No. We have not verified a Bolta-specific Paperclip plugin or CLI. The routes are the custom MCP connector and the optional skill import.

## Which agent runtime should hold the Bolta connection?

Use the one your social media agent already runs on, such as Claude Code, Codex, Cursor or OpenClaw. We have not confirmed every runtime can use company connectors, so test with the one you choose.

## Will a Paperclip heartbeat keep drafting if my computer sleeps?

No. Paperclip is self-hosted, so scheduled wake-ups depend on the machine and Paperclip staying up. We have not tested a long-running setup. A Bolta routine you switched on runs on Bolta's side and keeps going, and its drafts still wait for review.

## Which Paperclip actions should stay on Allowed?

Reads, such as listing accounts, reading the inbox and reading analytics. Paperclip's docs recommend starting writes at Off. Set save-post or create-routine to Ask first, and keep publish-post, approve-many-posts and delete-post Off.

## Paperclip cannot connect to https://mcp.bolta.ai/mcp

Check the full URL including /mcp and https. If it connects but calls fail with an auth error, the Authorization value may need the Bearer prefix. Paperclip's docs do not say which MCP transport it uses, and Bolta uses Streamable HTTP, so a transport mismatch is possible. If it fails, tell us which version of Paperclip you run.

## The OAuth window opens but never finishes

This has not been tested against Bolta. If Paperclip asks for a client you registered yourself, or the window never completes, remove the connector and add it again with a Bolta API key from Settings, API Keys.

## The agent says it has no Bolta tools

Check that this agent is allowed to use the connector and that the actions are not set to Off. Then use Refresh actions so Paperclip re-reads the tool list, and review the list afterwards.

## I installed the Bolta skill but the agent ignores it

Importing a skill does not attach it. Assign it to the agent. Some runtimes cannot sync skills, so if it still does nothing, rely on the connector instead.

## Bolta access stopped working after a while

Paperclip asks for a refresh token when the server supports one, but the provider decides whether to issue it, so an OAuth sign-in may need renewing. Reconnect the connector and sign in again. An API key avoids that, unless it has been revoked.

## A post saved but did not publish

That is intended. A saved draft stays a draft until you say yes. Read it in Bolta, approve it, then schedule or publish with your own yes.

## Paperclip is not Claude Code, Codex or OpenClaw

Those are agents that Paperclip can run. Paperclip is the layer above them that assigns jobs and holds the connector. If you only want one assistant and no org chart, connect Bolta straight to that assistant instead.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/claude-code](https://bolta.ai/integrations/claude-code)
- [Related page: /integrations/codex](https://bolta.ai/integrations/codex)
- [Related page: /integrations/cursor](https://bolta.ai/integrations/cursor)
- [Related page: /integrations/openclaw](https://bolta.ai/integrations/openclaw)
- [Related page: /integrations/mcp](https://bolta.ai/integrations/mcp)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [Paperclip official website](https://docs.paperclip.ing/)
