Loading...
Paperclip/TarenoPaperclip is a control plane: it organises agents into a company with goals, budgets and scheduled heartbeats, and launches a runtime for each.
Paperclip / Tareno
Watch what happens right after you connect Tareno: your assistant can see your social accounts, and you can start writing.
PaperclipIllustrated demo · no live account
Configure it in the agent's runtime. For a Claude Code adapter, add Tareno as an http server in user scope and sign in once as the same operating-system user that runs the heartbeat. For a Hermes adapter, enable the mcp toolset and define the server in Hermes's own config. Paperclip's documentation covers only these two adapters, and Tareno has not tested either with it.
Paperclip's guide documents MCP for the Claude Code and Hermes adapters. It expects other CLI adapters, such as Codex, Cursor Local or Gemini CLI, to inherit MCP from their own tools, but it does not cover that path yet, so do not assume it for them.
For Claude Code, the guide uses the claude mcp add command with the http transport and user scope for remote servers, because OAuth tokens should not sit in git. Use the address shown on the right. For Hermes, set the transport to http and a url under the server entry, and include mcp in the adapter's toolsets or the servers are ignored.
The guide says to complete the browser flow once as the same operating-system user that runs the heartbeat, using the /mcp command in an interactive claude session. Tokens persist and refresh. For Hermes, Tareno documents the hermes mcp login tareno command.
Run claude mcp get tareno in the agent's working directory with the environment the heartbeat uses, and look for OAuth configured. Then have the agent call your connected accounts in a run. The run viewer shows which tools were available, which is the check that the connection reached the agent.
claude mcp get tareno"url": "https://tareno.co/api/mcp"Input
Provide the approved source and audience.
Review-ready drafts
Use Tareno and compare the returned draft IDs.
Approval in Tareno
Review text, media, account, and time in Tareno and approve.
Paperclip is about many agents working toward goals on a schedule. These jobs use that structure, and each has a workflow guide.
When an agent has been working a goal for a week, the record exists in Paperclip: issues closed, budget used, what is blocked. A reporting agent can turn that into an X post about the work and save it as a draft, which you read against the tickets before any time is requested.
A company of agents produces a lot of activity that a human manager wants to learn from. A retrospective agent can summarise what worked and what failed over a month into a LinkedIn draft in the manager's voice, with the human deciding what to disclose publicly.
Paperclip tracks cost with monthly budgets and Tareno holds publishing as a pending action. A reporting agent that drafts weekly stays inside both limits, because its runs are small and its writes are drafts, and a person remains the only one who can turn any draft into a published post.
One guide for every network this agent can work with in Tareno, each with its own example, prompts and limits.
Hermes Agent and OpenClaw are agents with published Tareno skills. Paperclip sits above agents like them and decides when they run and within which budget. If you need a single agent that drafts, start with those pages. If you run several agents with goals and a manager, Paperclip is the layer that schedules them, and the Tareno connection stays in each runtime.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
No. Paperclip's documentation says it has no MCP command, because the control plane launches the runtime and the runtime speaks MCP. Tareno is therefore added in the Claude Code or Hermes configuration that the agent uses, and Paperclip only schedules the runs.
Claude Code and Hermes. The guide expects Codex, Cursor Local, Gemini CLI, OpenCode and Pi to inherit MCP from their own CLIs but says that path is not covered yet. Tareno makes no claim about those adapters.
You complete the OAuth flow once in an interactive session as the same operating-system user that runs the heartbeat. Tokens persist and refresh automatically. If the user differs, the heartbeat will not find the credential and the tool list will be empty.
Only partly. A project-level .mcp.json applies to agents working in that directory, while user scope and Hermes's YAML apply to everything run by that operating-system user. Because Tareno needs OAuth, user scope is the documented choice for remote servers.
No. Community projects with that name expose Paperclip's REST API to clients like Claude Code, so a person can manage Paperclip from a chat. They do not give Paperclip agents access to Tareno, and none is confirmed as official.
Not end to end. The steps come from Paperclip's own guide and Tareno's documented Claude Code and Hermes setups. Run claude mcp get tareno and a read-only call from the agent's directory before you let a heartbeat save drafts.
No. A scheduling or publishing request becomes an approval action in Tareno, and nothing reaches X or LinkedIn until you approve it in the dashboard. The agent can only report that the action is pending and read its status afterwards.
Usually `list_accounts` to confirm the destination, then `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything, and `get_action_status` tells you what became of the request.
Start with your Tareno account, connect your agent and prepare drafts. You approve what goes live.