Latest release v2026.1106.0 is live (November 6, 2026).
See what's newPaperclip works with MCP in both directions. Your agents can use any MCP server, with a rule for each action. Your own assistant can also control Paperclip through Paperclip’s MCP server.
npx paperclipai@latest onboard --yes
Open Connectors in Paperclip and choose Connect your own MCP server. Paste the server’s URL. Paperclip asks the server how to sign in, lists its actions and lets you set a rule for each one. You also choose which people and agents may use the connection.
Publish “Comparing agent runtimes” to the blog
You need the server’s http or https URL.
Open Connectors and choose Connect your own MCP server. Paste the URL.
Paperclip detects what the server needs. It runs an OAuth sign-in in the browser, asks for a key or connects with no sign-in.
Paperclip sorts the actions into read, write and destructive. Set each one to Allowed, Ask first or Off.
Pick the people and agents that may use the connection. After the server changes, choose Refresh actions.
On the Legacy runner, an agent can also use MCP servers from its own config file. The two paths behave differently.
| Question | Paperclip connector | Agent’s own config (Legacy runner) |
|---|---|---|
| Where do I set it up? | The Connectors page in Paperclip | On the host, for example with claude mcp add |
| Do Paperclip’s action rules apply? | Yes | No |
| Can a person approve a call first? | Yes, with Ask first | No |
| Who can use it? | The people and agents you choose | Every agent with that directory or OS user |
claude mcp addServers in an agent’s own config are not guaranteed to load in a Paperclip run. On Paperclip Runner, each session uses an isolated home. Use a connector when you can.
For the config path, see Add an MCP server to an agent.
Yes. Each Paperclip instance can serve MCP at /mcp/paperclip. With it, an assistant such as Claude Code or Codex can list agents, create tasks, add comments and read results. The feature is experimental and off by default.
Your instance needs sign-in accounts (authenticated mode) and an address the assistant can reach. Replace YOUR-PAPERCLIP-HOST with that address. Public use needs HTTPS.
An instance admin opens Settings, then Experimental, and turns on Assistant connections (MCP).
Run this command, then open /mcp in Claude Code to sign in.
claude mcp add --transport http paperclip https://YOUR-PAPERCLIP-HOST/mcp/paperclipAdd the server, then sign in with the scopes you want.
codex mcp add paperclip --url https://YOUR-PAPERCLIP-HOST/mcp/paperclip
codex mcp login paperclip --scopes paperclip:read,paperclip:write,paperclip:configure,offline_accessFollow the approval link and choose Connect organization. Then ask the assistant to call paperclip_connection to check that it works.
The two directions have different rules. A connector is governed by Paperclip. A server in an agent’s own config is not. Paperclip’s own MCP server is experimental.
Yes. Add it by URL on the Connectors page and set a rule for each action.
Not reliably. On Paperclip Runner, each session uses an isolated home, so servers in your own Claude Code config may not load. Add the server as a connector instead.
Turn on Assistant connections, then add https://YOUR-PAPERCLIP-HOST/mcp/paperclip as a remote MCP server. The steps are above.
No. It can list pending approvals and link you to Paperclip. You make the decision there.
paperclip.ing/mcp the same thing?No. That address serves read-only information about this website. It does not connect to any Paperclip instance.
“Give an agent a tool and a rule for each action. The agent moves fast on the safe actions, and a person decides the rest.”
Install Paperclip, paste a server URL and set the rules for its actions.