Paperclip

Add Honcho memory to Paperclip agents with the built-in Honcho connector

Paperclip has a built-in Honcho memory connector. It connects your Paperclip company to the Honcho MCP server at https://mcp.honcho.dev, and agents call Honcho tools when a task needs to recall or save something.

Memory connectors are experimental in Paperclip and off by default. They first shipped in v2026.1005.0; the workspace setting and agent instructions on this page need v2026.1012.0 or later.

​

Prerequisites

• Paperclip v2026.1012.0 or later
• A Honcho API key from app.honcho.dev

​

Connect Honcho

1. In Paperclip, open Settings → Experimental and turn on Memory connectors.
2. Open Connectors in the sidebar, find Honcho, and click Add key.
3. Paste your key into Honcho API key.
4. Enter the workspace agents should use in Honcho workspace. Both fields are required.
5. Choose which agents can use the connection, review the Agent instructions, and click Connect.

To change the workspace later, open the connection’s Permissions tab, edit Honcho workspace, and click Save workspace.

Turning Memory connectors off again hides setup for new connections. Existing connections keep running.

​

What Agents Get

• Honcho MCP tools. Every tool the Honcho MCP server exposes, such as chat, search, get_peer_context, add_messages_to_session, and create_conclusions.
• Agent instructions. A short paragraph Paperclip adds to the prompt of each agent that can use the connection. The default tells agents to recall preferences and prior decisions when work depends on earlier context, to save concise, durable facts after useful work, and never to store credentials or copy whole conversations.

Edit the instructions on the connection’s Permissions tab. Tell agents to use Honcho turns them off without removing tool access, and Reset to default restores the default text. Each agent’s Instructions tab shows the result under From connections. Agents receive the instructions only while Honcho workspace is set.

​

How Memory Is Organized

• Workspace: set by the connection. Paperclip fills in workspace_id on every tool that takes one and hides that argument from agents.
• Peers and sessions: agents choose them for each task, guided by the task and the agent instructions. Paperclip does not map issues or agents to Honcho on its own.
• Messages: nothing syncs in the background. Honcho stores only what agents save with tool calls.

To keep memory easy to find, describe a naming convention in the agent instructions. For example: one peer per agent, and one session per issue named after the issue identifier.

Honcho workspace picks the workspace tools run in. It does not restrict the API key. list_workspaces takes no workspace, so with an admin key agents can list every workspace on your Honcho instance. To keep agents in one workspace, create a key scoped to that workspace on the API Keys page.

​

Permissions

Each Honcho tool is an action on the connection’s Permissions tab. Set each one to Allowed (runs without approval), Ask first (a human approves each call), or Off (agents cannot run it).

Every action starts as Allowed, including writes and deletes. Paperclip classifies each action by its verb:

Class	Honcho tools
Read	Tools that get, list, search, or query, such as get_peer_context, list_conclusions, and search.
Write	Tools that create or add data, such as create_session and add_messages_to_session. Tools Paperclip cannot classify also count as writes, including chat and workspace_chat.
Destructive	delete_session, delete_conclusion, remove_peers_from_session, and remove_session_from_scope.

Set the destructive actions to Ask first or Off unless agents should delete memory on their own. Because chat and workspace_chat count as writes, setting every write to Ask first also adds an approval step to recall through those tools.

​

Deprecated: Honcho Plugin

The @honcho-ai/paperclip-honcho plugin is deprecated and no longer maintained. Version 0.1.4 is its final release. Use the built-in connector for new setups.

The connector works differently from the plugin. It does not sync issue comments or documents, adds no Memory tab to issues, and gives agents the Honcho MCP tools instead of the plugin’s honcho_* tools. To keep using memory the plugin already synced, set the connector’s Honcho workspace to the workspace the plugin created for your company. You can find it on the Explore page.

​

Next Steps

Honcho MCP

The server and tools behind the connector.

Paperclip Memory Connectors

Paperclip’s own notes on memory connectors.

Scoped API Keys

Create a key limited to one workspace.

Honcho Architecture

How workspaces, peers, and sessions fit together.