DEVELOPERS

Build cpcp into your workflow

cpcp exposes three stable surfaces: MCP for agents, a CLI for terminals, and a REST API for custom orchestration. They share the same transfer path and the same limits.

Create an API key Read the MCP guide

Quick start

Start with the shortest path. Use the CLI for scripts and terminals; use MCP for Claude Code, Codex, and Cursor.

CLI

Install the tarball published on this site, then send a file.

Install

npm install -g https://cp.1tools.vip/downloads/cpcp-cli-0.1.0.tgz

Send

cpcp upload ./report.pdf

Read the CLI guide

MCP

Add the remote MCP endpoint to your client; keep the token in a secret store or environment variable.

.cursor/mcp.json

{
  "mcpServers": {
    "cpcp": {
      "url": "https://cp.1tools.vip/mcp",
      "headers": {
        "Authorization": "Bearer cpcp_..."
      }
    }
  }
}

Read the MCP guide

Four integration surfaces

Choose the smallest surface that solves the job. Do not reimplement the same workflow in several places.

For agents and clients

MCP

A stateless JSON-RPC endpoint with cpcp_put_text, cpcp_put_file, and cpcp_get.

MCP guide

For scripts and CI

CLI

Send and pick up files from terminals and CI, with a pickup code and shareable link.

CLI guide

For server-side orchestration

REST API

Control init, upload, seal, and pickup directly for custom integrations.

API reference

For every MCP client

API keys

Create and revoke MCP tokens yourself; shown once and valid for 90 days.

Manage keys

Client setup

Commands for three common clients. Each guide includes verification and troubleshooting steps.

Claude Code

Write the remote MCP service into Claude Code with one command.

claude mcp add --transport http cpcp https://cp.1tools.vip/mcp --header "Authorization: Bearer cpcp_..."

Claude Code steps

Codex

Read the token from an environment variable instead of config.toml.

codex mcp add cpcp --url https://cp.1tools.vip/mcp --bearer-token-env-var CPCP_TOKEN

Codex steps

Cursor

Project or global mcp.json; confirm all tools in the MCP panel after saving.

~/.cursor/mcp.json

Cursor steps

Limits and boundaries

Text: 64KB per parcel
Single file: 100MB (MCP 5MB)
Parcel total: 20 files / 200MB
Claims: Up to 10
Retention: One hour
Token lifetime: 90 days

Security boundary

cpcp is not end-to-end encrypted. Content is stored briefly on the server and expires after one hour.
The pickup code is the credential. Anyone who obtains or guesses it can retrieve the content.
Keep tokens in a client secret store or environment variable, never in a repository, log, or prompt.
If a token leaks, revoke it on the API keys page before creating a replacement.

Start with one command

Create a token, or read the MCP guide. Neither path requires an account.

Create an API key Read the MCP guide