paperclip-mcp
Allows creating a Paperclip project, optionally linked to a GitHub repository.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@paperclip-mcpwhat needs my attention?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
paperclip-mcp
An MCP bridge to a Paperclip instance: its companies, its issues and whatever awaits a human decision, exposed to a remote MCP client (claude.ai, Claude Code, any compatible client).

A 48-second walkthrough is on the project page.
Why not the official MCP server
@paperclipai/mcp-server speaks stdio and exposes everything, approvals included,
plus free access to the API (paperclipApiRequest). This bridge exposes a closed
set of tools, each one subject to a policy.
Related MCP server: Accord
Policy per tool
policy.yaml gives each tool a mode:
Mode | Effect |
| the tool runs |
| the server asks for confirmation through MCP elicitation; a client that cannot ask is refused |
| the tool is not exposed (default for any tool missing from the file) |
Decision tools (issue_update, approval_decision, interaction_respond,
plan_confirm, action_request_decision, agent_resume, agent_unblock,
routine_run) only accept ask or deny: otherwise the server refuses to start.
issue_update_without_confirmation in policy.yaml lists the issue_update
changes that run directly: assignment (assign: true) and the listed statuses.
Any other change asks for confirmation. Most clients cannot ask yet, so those
changes are refused there.
The Paperclip token is a board token, with every board right: this server is the only thing that restricts them.
Tools
Tool | Effect |
| companies, issue prefix, id |
| what awaits a human, across companies |
| issues, detail, comments, documents, pending cards |
| agents of a company |
| pending approvals and tool actions |
| comment on an issue |
| create an issue, always unassigned, optionally in a project |
| assign an issue (agent or |
| list a company's projects, create one (optional GitHub repository) |
| runs in progress across companies, an agent's last runs, a run's status, error and last agent messages |
| what happened on an issue: status changes, assignments, comments, runs |
| tokens and runs per agent over the last days (subscription runs cost 0 cents) |
| latest events of a company, its recurring routines |
| pause an agent (cancels its run in progress), wake it without a comment |
| stop a run in progress |
| comment on an approval without deciding it |
| resume a paused agent, clear an agent's error, run a routine now; ask for confirmation |
| approve or reject an approval |
| answer a question card |
| accept or reject a plan |
| authorize or decline a suspended tool action |
In Paperclip, a comment only wakes the assigned agent, and an issue assigned to a
user wakes nobody. To make an agent act, issue_update assigns it, sets the status
to todo and adds a comment saying what to do.
Configuration
Variable | Role |
| default |
| dedicated board token |
| default |
| Cloudflare Access JWT validation, required |
| public hostname, otherwise the SDK answers 421 |
| local test without Cloudflare only |
Without CF_ACCESS_TEAM_DOMAIN and CF_ACCESS_AUD, the server refuses to start.
Run
docker build -t paperclip-mcp .
docker run -e PAPERCLIP_API_KEY=... -e CF_ACCESS_TEAM_DOMAIN=... -e CF_ACCESS_AUD=... \
-v ./policy.yaml:/app/policy.yaml:ro -p 9200:9200 paperclip-mcpThe MCP endpoint is /mcp, the health check /healthz.
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Remote MCP storefront for agent routing, verification, web extraction and x402-paid tools.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceActs as a gating proxy for MCP servers, merging tools and applying policy, verification, and audit layers.70 PyPI-
- AlicenseNot gradedqualityBmaintenanceProvides a policy-controlled MCP gateway that lets agents invoke tools with explicit policies, bounded execution, scoped visibility, and decision receipts.MIT
- AlicenseNot gradedqualityBmaintenanceEnables role-gated management of ops desk contacts, cases, and tasks via MCP, with tool schemas and availability filtered per role to enforce permission boundaries, over stdio or Streamable HTTP.MIT
- AlicenseNot gradedqualityBmaintenanceExposes a remote coding agent as MCP tools so an MCP client can delegate tasks, manage their lifecycle, and inspect the agent card, with permission decisions enforced inside the bridge.1Apache 2.0