Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/bruhsb/paperclip-mcp/llms.txt

Use this file to discover all available pages before exploring further.

Paperclip MCP ships as a lightweight Node.js process that speaks MCP’s stdio transport, making it compatible with every major AI coding assistant. You can run it directly via npx with no installation step, pull the pre-built container image from GitHub Container Registry, or spin up a full local Paperclip stack with a single Compose command. Pick the variant that matches your environment, then follow the host-specific guide below to drop in the exact config block your editor expects.

Installation variants

Three first-class variants are supported. All three expose the same 104 tools — the difference is only in the runtime environment.
VariantRequires Node.jsApprox. image sizeBest for
npm / npxYes (≥ 22)~no imageLocal dev, fastest startup
Docker / PodmanNo~186 MBCI, air-gapped hosts, isolated runtime
Compose stackNo~186 MB + serverFull local Paperclip + MCP in one command
The npm variant uses npx -y paperclip-mcp, which downloads and caches the package on first run. Subsequent starts use the cached copy — no re-download unless the version changes.

Required environment variables

Every variant requires the same four environment variables. Two optional variables are injected automatically by Paperclip during orchestrated agent runs.
VariableRequiredDescription
PAPERCLIP_API_KEYYesBearer token for API authentication
PAPERCLIP_API_URLYesBase URL of the Paperclip API, e.g. http://127.0.0.1:3100
PAPERCLIP_AGENT_IDYesUUID of the agent running this MCP server
PAPERCLIP_COMPANY_IDYesUUID of the company (used for company-scoped endpoints)
PAPERCLIP_RUN_IDNoHeartbeat run ID — injected automatically by Paperclip during agent runs
PAPERCLIP_REQUEST_TIMEOUT_MSNoHTTP request timeout in milliseconds (default: 30000)
The server exits immediately at startup if any required variable is absent. Check your environment config before restarting your MCP host.

Choose your MCP host

Follow the guide for your editor. Each page contains the exact config block, file location, and verification steps.

Claude Code

CLI (claude mcp add) and settings.json — npm and Docker variants covered.

Cursor

.cursor/mcp.json project or global config — npm and Docker variants covered.

VS Code

.vscode/mcp.json or user settings.json — npm and Docker variants covered.

Windsurf

Windsurf mcpServers config — npm and Docker variants covered.

Docker and Compose

If you prefer a containerised runtime or want to run the full Paperclip server alongside the MCP process, see the Docker guide.

Docker / Podman

Pre-built image, local build, networking, security hardening, and smoke testing.

Verification

Regardless of host or variant, verification is the same: open a chat with your AI assistant and ask “What paperclip tools do you have?” You should see 104 tools listed across domains including Issues, Agents, Approvals, Routines, Secrets, and more. If the count is lower or the server does not appear, consult the troubleshooting guide.

Build docs developers (and LLMs) love